Critical DNS Rebinding Vulnerability in Django Package (CVE-2016-9014)

py-django Updated 02 Oct 2025

Summary

09/12/2016
N/A
Yes i
High
8.1

ALPINE-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 conduct DNS rebinding attacks by leveraging failure to validate the HTTP Host heade... Affects py-django versions < 1.8.16-r0. Fixed in 1.8.16-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Django is a high-level Python web framework that encourages rapid development and clean, pragmatic design. It is widely used for building web applications and is known for its robustness and scalability. The framework includes features such as an ORM, authentication, and an admin interface. However, certain versions of Django are vulnerable to a DNS rebinding attack when the DEBUG setting is enabled, allowing attackers to exploit the application by manipulating the HTTP Host header.

Vulnerability Detail

The vulnerability arises from Django's failure to validate the HTTP Host header against the settings.ALLOWED_HOSTS when settings.DEBUG is set to True. This oversight can allow remote attackers to conduct DNS rebinding attacks, potentially leading to unauthorized access to sensitive data or control over the application. The affected versions include Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3. The CVSS score for this vulnerability is 8.1, indicating a high severity level.

How To Fix

Minimum fixed version

1.8.16-r0

This is the first release that contains the fix.

sudo apk add --upgrade py-django

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, consider disabling the DEBUG setting in your Django settings file by setting 'DEBUG = False'. This will prevent the vulnerability from being exploited until you can apply the necessary updates.

Conclusion

In summary, CVE-2016-9014 is a significant vulnerability affecting various versions of the Django package, allowing for potential DNS rebinding attacks. It is crucial to update to the patched versions or implement workarounds to protect your application from exploitation.

See every vulnerability recorded for py-django →

Share this vulnerability

FAQ

CVE-2016-9014 is a critical vulnerability in Django that allows remote attackers to conduct DNS rebinding attacks when the DEBUG setting is enabled.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The affected versions include Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3.

The CVSS score for this vulnerability is 8.1, indicating a high severity level.

If you cannot update immediately, ensure that the DEBUG setting is set to False in your Django settings file to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for py-django.

How To Fix

Minimum fixed version

1.8.16-r0

This is the first release that contains the fix.

sudo apk add --upgrade py-django

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback