CVE-2016-9014: 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…
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 6% (FIRST EPSS); higher than 93.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: py-django (Alpine:v3.10) 1.8.16-r0; py3-django (Alpine:v3.11) 1.8.16-r0; python-django (Debian:12) 1:1.10.3-1.
Low priority for now. Upgrade to py-django (Alpine:v3.10) 1.8.16-r0; py3-django (Alpine:v3.11) 1.8.16-r0; python-django (Debian:12) 1:1.10.3-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 9, 2016
- Updated
- Jun 16, 2026
- EPSS
- 6.0% · 93th percentile
- CWE
- CWE-264
Report tools
Action score
34
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| djangoproject | django | cpe:2.3:a:djangoproject:django |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux16.10
- djangoproject django1.10
- djangoproject django1.10.1
- djangoproject django1.10.2
- djangoproject django1.8
+12 more rows
- djangoproject django1.8.1
- djangoproject django1.8.10
- djangoproject django1.8.11
- djangoproject django1.8.12
- djangoproject django1.8.13
- djangoproject django1.8.14
- djangoproject django1.8.15
- djangoproject django1.8.2
- djangoproject django1.8.3
- djangoproject django1.8.4
- djangoproject django1.8.5
- djangoproject django1.8.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | py-django | before 1.8.16-r0 | 1.8.16-r0 |
| Alpine:v3.11 | py3-django | before 1.8.16-r0 | 1.8.16-r0 |
| Debian:12 | python-django | before 1:1.10.3-1 | 1:1.10.3-1 |
| Debian:7 | python-django | before 1.4.22-1+deb7u2 | 1.4.22-1+deb7u2 |
| Debian:8 | python-django | before 1.7.11-1+deb8u2 | 1.7.11-1+deb8u2 |
| PyPI | django | from 1.10 · before 1.10.3 | 1.10.3 |
| PyPI | django | from 1.10a1 · before 1.10.3 | 1.10.3 |
| PyPI | django | from 1.8a1 · before 1.8.16 | 1.8.16 |
| PyPI | django | from 1.9 · before 1.9.11 | 1.9.11 |
| PyPI | django | from 1.9a1 · before 1.9.11 | 1.9.11 |
| PyPI | django | before 1.8.16 | 1.8.16 |
| SUSE:OpenStack Cloud 6 | python-Django | before 1.8.19-3.6.1 | 1.8.19-3.6.1 |
| SUSE:OpenStack Cloud 7 | python-Django | before 1.8.19-3.4.1 | 1.8.19-3.4.1 |
Same product
fedoraproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1111DHCP packages in Red Hat Enterprise Linux 6 and 7, Fedora 28, and earlier are vulnerable to a command injection flaw in the NetworkManager…59Plan
- CVE-2024-24576Rusts's `std::process::Command` did not properly escape arguments of batch files on Windows46Plan
- CVE-2016-7167Multiple integer overflows in the (1) curl_escape, (2) curl_easy_escape, (3) curl_unescape, and (4) curl_easy_unescape functions in libcurl…43Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-5386Jul 18, 2016 · The net/http package in Go through 1.6 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not…34Monitor
- ← EarlierCVE-2016-5384Aug 12, 2016 · fontconfig before 2.12.1 does not validate offsets, which allows local users to trigger arbitrary free calls and consequently conduct…31Monitor
- Later →CVE-2016-2090Jan 13, 2017 · Off-by-one vulnerability in the fgetwln function in libbsd before 0.8.2 allows attackers to have unspecified impact via unknown vectors…40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:py-django | 1.8.16-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:py3-django | 1.8.16-r0 · Alpine:v3.11 | Package registry (OSV) |
| debian:python-django | 1:1.10.3-1 · Debian:12 | Package registry (OSV) |
| PyPI:django | 1.10.3 | Package registry (OSV) |
| PyPI:django | 1.8.16 | Package registry (OSV) |
| PyPI:django | 1.9.11 | Package registry (OSV) |
| suse:python-Django | 1.8.19-3.4.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- www.securityfocus.com/bid/94068
- www.securitytracker.com/id/1037159
- www.ubuntu.com/usn/USN-3115-1
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OG5ROMUPS6C7BXELD3TAUUH7OBYV56WQ/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QXDKJYHN74BWY3P7AR2UZDVJREQMRE6S/
- www.djangoproject.com/weblog/2016/nov/01/security-releases/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.