Django Image Field Vulnerable to Image Decompression Bombs
Published Jul 31, 2012 · Updated Oct 23, 2026 · Also known as PYSEC-2012-3, GHSA-59w8-4wm2-4xw8
Original summary
Normalized public record · Updated Oct 23, 2026
Django Image Field Vulnerable to Image Decompression Bombs
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
The `django.forms.ImageField` class in the form system in Django before 1.3.2 and 1.4.x before 1.4.1 completely decompresses image data during image validation, which allows remote attackers to cause a denial of service (memory consumption) by uploading an image file.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- PYSEC-2012-3, GHSA-59w8-4wm2-4xw8
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- [oss-security] 20120730 CVE Request: Django 1.3.1 and 1.4.0 security issues ↗
- www.djangoproject.com ↗
- MDVSA-2012:143 ↗
- USN-1560-1 ↗
- [oss-security] 20120730 Re: CVE Request: Django 1.3.1 and 1.4.0 security issues ↗
- DSA-2529 ↗
Record history
Published Jul 31, 2012 · Last refreshed Oct 23, 2026