# Nginx security advisory (CVE-2016-0742, CVE-2016-0746, CVE-2016-0747)

**URL:** <https://www.ruby-forum.com/t/nginx-security-advisory-cve-2016-0742-cve-2016-0746-cve-2016-0747/243934>\
**Category:** NGINX\
**Created:** [January 26, 2016, 5:33pm UTC](https://www.ruby-forum.com/t/nginx-security-advisory-cve-2016-0742-cve-2016-0746-cve-2016-0747/243934 "2016-01-26T17:33:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [January 26, 2016, 5:33pm UTC](https://www.ruby-forum.com/t/nginx-security-advisory-cve-2016-0742-cve-2016-0746-cve-2016-0747/243934/1 "2016-01-26T17:33:52Z")

</div>

Hello!

Several problems in nginx resolver were identified, which might  
allow an attacker to cause worker process crash, or might have  
potential other impact:

- Invalid pointer dereference might occur during DNS server response  
processing, allowing an attacker who is able to forge UDP  
packets from the DNS server to cause worker process crash  
(CVE-2016-0742).

- Use-after-free condition might occur during CNAME response  
processing. This problem allows an attacker who is able to trigger  
name resolution to cause worker process crash, or might  
have potential other impact (CVE-2016-0746).

- CNAME resolution was insufficiently limited, allowing an attacker who  
is able to trigger arbitrary name resolution to cause excessive  
resource  
consumption in worker processes (CVE-2016-0747).

The problems affect nginx 0.6.18 - 1.9.9 if the “resolver” directive  
is used in a configuration file.

The problems are fixed in nginx 1.9.10, 1.8.1.

–  
Maxim D.  
[http://nginx.org/](http://nginx.org/)