CVE-2015-8870

Integer overflow in tools/bmp2tiff.c in LibTIFF before 4.0.4 allows remote attackers to cause a denial of service (heap-based buffer over-read), or possibly obtain sensitive information from process memory, via crafted width and length values in RLE4 or RLE8 data in a BMP file.

Published: 2016-12-06 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2015-8870 is rated Moderate Risk (58.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.00%). EPSS rose +1.26% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2015-8870

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.74% 2.00% +1.26%
2 2026-03-25 0.39% 0.74% +0.35%
3 2026-01-21 — 0.39% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2015-8870

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.4 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.2 [email protected]
5.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 4.9 [email protected]

Weakness enumeration for CVE-2015-8870

OS Trackers for CVE-2015-8870

vendor priority summary link
debian not yet assigned CVE-2015-8870 not yet assigned priority: Debian including 1 source packages (tiff), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2015-8870
redhat medium — https://access.redhat.com/security/cve/CVE-2015-8870
suse medium CVE-2015-8870 severity moderate: SUSE including 14 source package names (libtiff-4.0.3-27.el7_3, libtiff-devel, …), 33 product×package rows across 11 product lines (SUSE Liberty Linux 7, SUSE Linux Enterprise Desktop 12 SP1, … (11 product lines)): Fixed 20, Known Not Affected 13. https://www.suse.com/security/cve/CVE-2015-8870/
ubuntu medium CVE-2015-8870 medium priority: Ubuntu including 1 source packages (tiff), 6 status rows across 6 suites (precise, trusty, upstream, xenial, yakkety, zesty): not-affected 5, needs-triage 1. https://ubuntu.com/security/CVE-2015-8870

Affected software / configurations for CVE-2015-8870

Vendor Product Version Raw CPE
libtiff libtiff <= 4.0.3 cpe:2.3:a:libtiff:libtiff:*:*:*:*:*:*:*:*

References for CVE-2015-8870

cvelogic Threat Intelligence