Bug 1302589 - (CVE-2016-0747) CVE-2016-0747 nginx: Insufficient limits of CNAME resolution in resolver
CVE-2016-0747 nginx: Insufficient limits of CNAME resolution in resolver
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20160126,repor...
: Security
Depends On: 1302334 1302337 1302592 1302599 1342443
Blocks: 1302591
  Show dependency treegraph
 
Reported: 2016-01-28 03:41 EST by Martin Prpič
Modified: 2016-07-14 07:21 EDT (History)
13 users (show)

See Also:
Fixed In Version: nginx 1.9.10, nginx 1.8.1
Doc Type: Bug Fix
Doc Text:
It was discovered that nginx did not limit recursion when resolving CNAME DNS records. An attacker able to manipulate DNS responses received by nginx could use this flaw to cause a worker process to use an excessive amount of resources if nginx enabled the resolver in its configuration.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-14 07:21:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Prpič 2016-01-28 03:41:47 EST
The following flaw was found in the nginx resolver:

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

This issue affects nginx only if the "resolver" directive is used in a configuration file.

The problems are fixed in nginx upstream versions 1.9.10 and 1.8.1.

External References:

http://mailman.nginx.org/pipermail/nginx-announce/2016/000169.html
Comment 1 Martin Prpič 2016-01-28 03:45:15 EST
Created nginx tracking bugs for this issue:

Affects: fedora-all [bug 1302592]
Comment 3 Tomas Hoger 2016-02-10 16:40:12 EST
The nginx' DNS resolver is not enabled by default.  It can be used to dynamically resolve names of backend servers.  Therefore, in many configurations, attacker would not be able to make nginx resolve names in attacker controlled domain (backend servers and their name are usually considered trusted) without being able to MITM DNS traffic between nginx and configured DNS server (or the configured DNS server/resolver and authoritative DNS servers for the zone with names being resolved).  If resolver is not used, backend server names specified in configuration are resolved to IP addresses at start.
Comment 6 errata-xmlrpc 2016-07-14 01:50:31 EDT
This issue has been addressed in the following products:

  Red Hat Software Collections for Red Hat Enterprise Linux 7.2 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7.1 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7
  Red Hat Software Collections for Red Hat Enterprise Linux 6
  Red Hat Software Collections for Red Hat Enterprise Linux 6.6 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 6.7 EUS

Via RHSA-2016:1425 https://access.redhat.com/errata/RHSA-2016:1425

Note You need to log in before you can comment on or make changes to this bug.