CVE-2016-9014: Django DNS rebinding vulnerability in Host header validation

CVE-2016-9014 · Severity: low · CVSS 3 · Published 2016-12-09

Django, a widely-used Python web framework, did not properly validate HTTP Host headers when running in debug mode, allowing attackers to conduct DNS rebinding attacks. DNS rebinding is a technique where an attacker tricks a browser into making requests to unintended targets by manipulating DNS responses. This vulnerability could allow an attacker to bypass security controls and gain unauthorized access to Django applications running in debug mode.

Technologies: Django (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2016-9014 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-9014 being exploited in the wild.
How severe is CVE-2016-9014?
Low severity, with a CVSS score of 3, published 9 December 2016.
Which products and versions are affected?
Django (PyPI) ECOSYSTEM:introduced=0,fixed=1.8.16,introduced=1.9,fixed=1.9.11,introduced=1.10,fixed=1.10.3, ECOSYSTEM:introduced=1.8a1,fixed=1.8.16.
Is there a fix for CVE-2016-9014?
Yes. Django (PyPI): upgrade to 1.10.3, 1.8.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-9014 attacked?
It is attacked over the network.
Am I affected by CVE-2016-9014?
Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Django (PyPI): upgrade to 1.10.3, 1.8.16 or later
    pip install "Django>=1.10.3"

Technical details

The vulnerability exists in Django versions 1.8 before 1.8.16, 1.9 before 1.9.11, and 1.10 before 1.10.3 when settings.DEBUG is True. The root cause is insufficient validation of the HTTP Host header against the settings.ALLOWED_HOSTS configuration. An attacker can perform a DNS rebinding attack by first resolving a domain to the attacker's IP, then after the browser connects, changing the DNS record to resolve to the target Django application's address. Because the Host header is not validated, the application accepts requests with a malicious Host header. This allows an attacker to bypass host-based access controls. The fix validates the Host header against ALLOWED_HOSTS and rejects requests with invalid hosts, even when DEBUG is enabled.

Affected products

  • Django Django 1.8 before 1.8.16, 1.9 before 1.9.11, 1.10 before 1.10.3

Identifiers

  • CVE-2016-9014
  • GHSA-3f2c-jm6v-cr35
  • PYSEC-2016-18

Timeline

  • 2016-11-01: disclosed: Security releases published by Django project
  • 2016-11-01: patched: Fixes released in Django 1.8.16, 1.9.11, and 1.10.3
  • 2022-05-17: advisory: GHSA-3f2c-jm6v-cr35 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.