CVE-2010-3087 json
LibTIFF before 3.9.2-5.2.1 in SUSE openSUSE 11.3 allows remote attackers to cause a denial of service (memory corruption) or possibly execu…
published 2010-09-28 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-3088
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
LibTIFF before 3.9.2-5.2.1 in SUSE openSUSE 11.3 allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via a crafted TIFF image.
Patch / fix
- tiff Debian 14, Debian 13, Debian 12 3.9.4-5
debian advisories DEBIAN-CVE-2010-3087
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-3087 updated cvss 7.5
libtiff: DoS or possible arbitrary code execution via crafted TIFF image
-
Red Hat Enterprise Linux 4 libtiff Red Hat Enterprise Linux 5 libtiff Red Hat Enterprise Linux 6 libtiffnot 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
3.24% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
security.gentoo.org
/glsa/glsa-201209-02.xml
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2010-09/msg00006.html
vendor-advisory
- bugzilla.novell.com /show_bug.cgi?id=624215
- blackberry.com /btsc/KB27244
- support.novell.com /security/cve/CVE-2010-3087.html
-
secunia.com
/advisories/50726
third-party-advisory
Sources
- CVE List CVE-2010-3087
- NVD CVE-2010-3087
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.