Skip to content
Fencer Intel
medium 4.3

CVE-2010-2482 json

LibTIFF 3.9.4 and earlier does not properly handle an invalid td_stripbytecount field, which allows remote attackers to cause a denial of s…

published 16y ago modified 4mo ago also EUVD-2010-2488

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.8%
EPSS 8.8% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

LibTIFF 3.9.4 and earlier does not properly handle an invalid td_stripbytecount field, which allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted TIFF file, a different vulnerability than CVE-2010-2443.

Patch / fix

  • tiff Debian 14, Debian 13, Debian 12 3.9.4-1

debian advisories DEBIAN-CVE-2010-2482

Is CVE-2010-2482 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2010-2482 updated cvss 4.3

libtiff: OJPEGReadBufferFill NULL deref crash

  • 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

Timeline

  1. Published
  2. First public exploit (EDB-14573)

Exploit prediction

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

Exploits and checks

  • EDB-14573 LibTIFF - 'td_stripbytecount' Null Pointer Dereference Remote Denial of Service dos, 2010-08-07
  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=603024 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

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.