Upstream information

CVE-2014-0481 at MITRE

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.

SUSE information

Overall state of this security issue: Resolved

This issue is currently rated as having moderate severity.

CVSS v2 Scores
  National Vulnerability Database
Base Score 4.3
Vector AV:N/AC:M/Au:N/C:N/I:N/A:P
Access Vector Network
Access Complexity Medium
Authentication None
Confidentiality Impact None
Integrity Impact None
Availability Impact Partial
SUSE Bugzilla entries: 893088 [NEW], 919763 [RESOLVED]

SUSE Security Advisories:

List of released packages

Product(s) Fixed package version(s) References
SUSE OpenStack Cloud 3.0
  • python-django >= 1.5.10-0.8.1
Patchnames:
sleclo30sp3-python-django
SUSE OpenStack Cloud 4
  • python-django >= 1.5.10-0.11.1
Patchnames:
sleclo40sp3-python-django
SUSE Cloud 3
  • python-django >= 1.5.10-0.8.1
Builds
SAT Patch Nr: 9685
SUSE Cloud 4
  • python-django >= 1.5.10-0.11.1
Builds
SAT Patch Nr: 9684
openSUSE 13.1
  • python-django >= 1.5.10-0.2.8.1
Patchnames:
openSUSE-2014-542


Status of this issue by product and package

Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification.

Product(s) Source package State
SUSE Cloud 11.3 python-django Released
SUSE Cloud 2.0 python-django Released
SUSE Cloud 3 python-django Released
SUSE Cloud 4 python-django Released