CVE-2005-1544 in the critical feed json
Stack-based buffer overflow in libTIFF before 3.7.2 allows remote attackers to execute arbitrary code via a TIFF file with a malformed Bits…
published 2005-05-14 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-1547
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.4%
- EPSS 14.4% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Stack-based buffer overflow in libTIFF before 3.7.2 allows remote attackers to execute arbitrary code via a TIFF file with a malformed BitsPerSample tag.
Patch / fix
- tiff Debian 14, Debian 13, Debian 12 3.7.2-3
debian advisories DEBIAN-CVE-2005-1544
Timeline
- Published
- First public exploit (EDB-1554)
Exploit prediction
14.39% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-1554 LibTiff 3.7.1 - BitsPerSample Tag Local Buffer Overflow local, 2006-03-05
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
bugs.gentoo.org
/show_bug.cgi?id=91584
patch
-
debian.org
/security/2005/dsa-755
vendor-advisory
-
gentoo.org
/security/en/glsa/glsa-200505-07.xml
vendor-advisory
-
mandriva.com
/security/advisories?name=MDKSA-2006:042
vendor-advisory
-
ubuntu.com
/usn/usn-130-1
vendor-advisory
- bugzilla.remotesensing.org /show_bug.cgi?id=843
-
secunia.com
/advisories/18289
third-party-advisory
-
secunia.com
/advisories/16872
third-party-advisory
-
secunia.com
/advisories/15320
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/20533
vdb-entry
-
secunia.com
/advisories/18943
third-party-advisory
-
osvdb.org
/16350
vdb-entry
-
securitytracker.com
/id?1013944
vdb-entry
-
securityfocus.com
/bid/13585
vdb-entry
Sources
- CVE List CVE-2005-1544
- NVD CVE-2005-1544
Fencer Vulns 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.