Skip to content
Fencer Intel
high 7.5

CVE-2015-0221 json

Django DoS in django.views.static.serve

published 11y ago modified 4mo ago also GHSA-jhjg-w2cp-5j44 , PYSEC-2015-6 , EUVD-2015-0015

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

Summary

The django.views.static.serve view in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 reads files an entire line at a time, which allows remote attackers to cause a denial of service (memory consumption) via a long line in a file.

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-0221

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

ubuntu advisories UBUNTU-CVE-2015-0221

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

Is CVE-2015-0221 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-0221 updated cvss 4.3

Django: denial of service attack against django.views.static.serve

  • 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

4.45% chance of exploitation in the next 30 days, higher than 91% 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:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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-399 Resource Management Errors
  • CWE-400 Uncontrolled Resource Consumption
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.