ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2014-0481

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…

Published Aug 26, 2014 · catalog updated Jun 17, 2026 · the affected product

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2014-0481. EPSS is 2.45%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium4.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
2.45%
Remediation
Version ranges on file
Affected products
cpe djangoproject/django · cpe opensuse project/opensuse · cpe opensuse/opensuse

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe djangoproject/django1.4
  • cpe djangoproject/django1.4.1
  • cpe djangoproject/django1.4.2
  • cpe djangoproject/django<= 1.4.13
  • cpe opensuse project/opensuse12.3
  • cpe opensuse/opensuse13.1

How to fix CVE-2014-0481

  • Upgrade

    CVE-2014-0481 lists a fix boundary at 1.4.13. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <= 1.4.13

  • Advisory

    Open the inventory_high record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2014-0481. EPSS is 2.45%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Compare what you have installed with opensuse project/opensuse 12.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-399. EPSS 2.45%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 26, 2014 · Monitored products — high

    Detected

    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.

  2. Jun 17, 2026 · Monitored products — high

    Updated

    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.

Sources

  • Monitored products — highVendor advisoryCVE-2014-0481

    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.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Monitored products — highNov 7, 2026