CVE-2015-0219
UnknownEPSS 6.78%
Last modified
CVE-2015-0219 is a vulnerability of currently unknown severity. Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X-Auth_User header.. EPSS estimates a 6.78% chance of exploitation in the next 30 days.
Description
Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X-Auth_User header.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Djangoproject | Django | <= 1.4.17 |
| Djangoproject | Django | 1.6 |
| Djangoproject | Django | 1.6.1 |
| Djangoproject | Django | 1.6.2 |
| Djangoproject | Django | 1.6.3 |
| Djangoproject | Django | 1.6.4 |
| Djangoproject | Django | 1.6.5 |
| Djangoproject | Django | 1.6.6 |
| Djangoproject | Django | 1.6.7 |
| Djangoproject | Django | 1.6.8 |
| Djangoproject | Django | 1.6.9 |
| Djangoproject | Django | 1.7 |
| Djangoproject | Django | 1.7.1 |
| Djangoproject | Django | 1.7.2 |
References
- http://www.ubuntu.com/usn/USN-2469-1Patch, Vendor Advisory
- https://www.djangoproject.com/weblog/2015/jan/13/security/Exploit, Patch, Vendor Advisory
- http://www.ubuntu.com/usn/USN-2469-1Patch, Vendor Advisory
- https://www.djangoproject.com/weblog/2015/jan/13/security/Exploit, Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2015-0219?
Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X-Auth_User header.
How severe is CVE-2015-0219?
Severity scoring for CVE-2015-0219 is pending analysis. The EPSS model estimates a 6.78% probability of exploitation in the next 30 days.
How do I fix CVE-2015-0219?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2015-0219?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST