Skip to content
Fencer Intel
medium 5.3

CVE-2015-0219 json

Django WSGI Header Spoofing Vulnerability

published 11y ago modified 4mo ago also GHSA-7qfw-j7hp-v45g , PYSEC-2015-4 , EUVD-2015-0013

cvss
5.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
7.0%
EPSS 7.0% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi django 1.4.18, 1.6.10, 1.7.3
  • python-django Debian 14, Debian 13, Debian 12 1.7.1-1.1

debian advisories DEBIAN-CVE-2015-0219

  • python-django Ubuntu 14.04 LTS 1.6.1-2ubuntu0.6

ubuntu advisories UBUNTU-CVE-2015-0219

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • python-Django Enterprise Storage 1.0 1.6.11-4.1

suse advisories SUSE-SU-2015:1109-1SUSE-SU-2015:1112-1

  • python-bjoern openSUSE Tumbleweed 3.2.2-2.6
  • python-bjoern openSUSE Tumbleweed 3.2.2-1.10
  • python-bjoern openSUSE Tumbleweed 1.4.2-1.23

opensuse advisories openSUSE-SU-2026:12000-1openSUSE-SU-2024:14133-1openSUSE-SU-2024:10206-1

Is CVE-2015-0219 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-0219 updated cvss 5.8

Django: WSGI header spoofing via underscore/dash conflation

  • Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) python-django Red Hat Enterprise Linux OpenStack Platform 6 (Juno) python-django Red Hat OpenStack Platform 4 Django14 Red Hat Subscription Asset Manager Django
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.97% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • djangoproject.com https://www.djangoproject.com/weblog/2015/jan/13/security/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi django
<1.4.18
>=1.6, <1.6.10
>=1.7, <1.7.3
>=1.5, <1.6.10
1.4.18
1.6.10
1.7.3

Classification

Weakness
  • CWE-17 DEPRECATED: Code
  • CWE-290 Authentication Bypass by Spoofing
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.