CVE-2014-0481

Description

The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a denial of service (CPU consumption) by unloading a multiple files with the same name.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
2.449%
chance of exploitation in the next 30 days
higher than 84.7% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2014-08-26Published by the CNA14:00 UTC
  2. 2022-05-14GitHub advisory published (GHSA-296w-6qhq-gf92)2818 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-296w-6qhq-gf92, affected packages:

PackageVulnerable versionsFixed in
PyPI djangobefore 1.4.141.4.14
PyPI djangofrom 1.5 before 1.5.91.5.9
PyPI djangofrom 1.6 before 1.6.61.6.6

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
djangoproject django1.4no fix listed1.4.1no fix listed1.4.10no fix listed1.4.11no fix listed1.4.12no fix listed(+24 more)not listednot listednot listednot listednot listed
debian debian_linux7.0no fix listednot listed
opensuse opensuse13.1no fix listednot listed
opensuse_project opensuse12.3no fix listednot listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources