Skip to content
Fencer Intel
high 7.5

CVE-2012-3444 json

Django vulnerable to Improper Restriction of Operations within the Bounds of a Memory Buffer

published 2012-07-31 14 y ago modified 2026-06-16 4 mo ago also GHSA-5h2q-4hrp-v9rr , PYSEC-2012-4 , EUVD-2012-0005

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

The get_image_dimensions function in the image-handling functionality in Django before 1.3.2 and 1.4.x before 1.4.1 uses a constant chunk size in all attempts to determine dimensions, which allows remote attackers to cause a denial of service (process or thread consumption) via a large TIFF image.

Patch / fix

  • pypi django 1.3.2, 1.4.1
  • python-django Debian 14, Debian 13, Debian 12 1.4.1-1

debian advisories DEBIAN-CVE-2012-3444

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-3444 updated cvss 4.3

Django: 1.3.1 and 1.4.0 Denial-of-service via get_image_dimensions()

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi django
<1.3.2
>=1.4, <1.4.1
1.3.2
1.4.1

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.