dbcve.org
FedoraOperating system · Fedoraproject

CVE-2016-9014

HIGH · 8.1 CVSS v3.0 Published 2016-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3, when settings.DEBUG is True, allow remote attackers to conduct DNS rebinding attacks by leveraging failure to validate the HTTP Host header against settings.ALLOWED_HOSTS.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Django versions before 1.8.16, 1.9.11, and 1.10.3 fail to validate the HTTP Host header against settings.ALLOWED_HOSTS when DEBUG=True. This allows DNS rebinding attacks where an attacker uses a malicious DNS response to bypass security controls and inject arbitrary Host headers, potentially enabling cache poisoning or session hijacking.

MitigationSet DEBUG=False in production environments and ensure settings.ALLOWED_HOSTS contains only legitimate domain names. Additionally, upgrade Django to a patched version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 24= 25
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 16.04= 16.10
DjangoFramework / library
Affected:= 1.8= 1.8.1= 1.8.2= 1.8.3= 1.8.4= 1.8.5= 1.8.6= 1.8.7= 1.8.8= 1.8.9= 1.8.10= 1.8.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Django version
    Run 'django-admin --version' or check your requirements.txt/dependencies file for the django package version
    Affected if The installed version is 1.8.x before 1.8.16, 1.9.x before 1.9.11, or 1.10.x before 1.10.3
  2. Locate Django settings file
    Find your project's settings.py file, typically in the project root under a subdirectory named after your project
    Affected if Unable to locate settings file for inspection
  3. Check DEBUG setting value
    Open settings.py and search for the DEBUG variable definition. Verify if it is set to True
    Affected if DEBUG is set to True in your production or accessible environment
  4. Verify ALLOWED_HOSTS configuration
    In settings.py, locate the ALLOWED_HOSTS setting and examine its value
    Affected if ALLOWED_HOSTS is empty, contains only empty strings, or contains a wildcard '*'

You are affected if your Django version falls within the vulnerable ranges (1.8.x before 1.8.16, 1.9.x before 1.9.11, 1.10.x before 1.10.3) AND DEBUG=True AND ALLOWED_HOSTS is empty or misconfigured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Set DEBUG=False in production environments and ensure settings.ALLOWED_HOSTS contains only legitimate domain names. Additionally, upgrade Django to a patched version.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-9014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-9014 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data