CVE-2014-0481 : Detail

CVE-2014-0481

3.02%V3
Network
2014-08-26
12h00 +00:00
2017-01-04
16h57 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

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.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-399 Category : Resource Management Errors
Weaknesses in this category are related to improper management of system resources.

Metrics

Metrics Score Severity CVSS Vector Source
V2 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Products Mentioned

Configuraton 0

Opensuse>>Opensuse >> Version 13.1

Opensuse_project>>Opensuse >> Version 12.3

Configuraton 0

Djangoproject>>Django >> Version To (including) 1.4.13

Djangoproject>>Django >> Version 1.4

Djangoproject>>Django >> Version 1.4.1

Djangoproject>>Django >> Version 1.4.2

Djangoproject>>Django >> Version 1.4.4

Djangoproject>>Django >> Version 1.4.5

Djangoproject>>Django >> Version 1.4.6

Djangoproject>>Django >> Version 1.4.7

Djangoproject>>Django >> Version 1.4.8

Djangoproject>>Django >> Version 1.4.9

Djangoproject>>Django >> Version 1.4.10

Djangoproject>>Django >> Version 1.4.11

Djangoproject>>Django >> Version 1.4.12

Configuraton 0

Djangoproject>>Django >> Version 1.5

Djangoproject>>Django >> Version 1.5

Djangoproject>>Django >> Version 1.5

Djangoproject>>Django >> Version 1.5.1

Djangoproject>>Django >> Version 1.5.2

Djangoproject>>Django >> Version 1.5.3

Djangoproject>>Django >> Version 1.5.4

Djangoproject>>Django >> Version 1.5.5

Djangoproject>>Django >> Version 1.5.6

Djangoproject>>Django >> Version 1.5.7

Djangoproject>>Django >> Version 1.5.8

Configuraton 0

Djangoproject>>Django >> Version 1.7

Djangoproject>>Django >> Version 1.7

Djangoproject>>Django >> Version 1.7

Djangoproject>>Django >> Version 1.7

Djangoproject>>Django >> Version 1.7

Djangoproject>>Django >> Version 1.7

Configuraton 0

Djangoproject>>Django >> Version 1.6

Djangoproject>>Django >> Version 1.6

Djangoproject>>Django >> Version 1.6

Djangoproject>>Django >> Version 1.6

Djangoproject>>Django >> Version 1.6

Djangoproject>>Django >> Version 1.6.1

Djangoproject>>Django >> Version 1.6.2

Djangoproject>>Django >> Version 1.6.3

Djangoproject>>Django >> Version 1.6.4

Djangoproject>>Django >> Version 1.6.5

Configuraton 0

Debian>>Debian_linux >> Version 7.0

References

http://secunia.com/advisories/61276
Tags : third-party-advisory, x_refsource_SECUNIA
http://secunia.com/advisories/61281
Tags : third-party-advisory, x_refsource_SECUNIA
http://www.debian.org/security/2014/dsa-3010
Tags : vendor-advisory, x_refsource_DEBIAN
http://secunia.com/advisories/59782
Tags : third-party-advisory, x_refsource_SECUNIA