CVE-2017-2888

Exp

An exploitable integer overflow vulnerability exists when creating a new RGB Surface in SDL 2.0.5. A specially crafted file can cause an integer overflow resulting in too little memory being allocated which can lead to a buffer overflow and potential code execution. An attacker can provide a specially crafted image file to trigger this vulnerability.

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

CVE-2017-2888 is rated High Exploit Risk (82.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 3.07%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +1.87% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2017-2888

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2017-2888

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 1.21% 3.07% +1.87%
2 2026-06-14 1.63% 1.21% -0.42%
3 2026-04-02 — 1.63% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-2888

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/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:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-2888

OS Trackers for CVE-2017-2888

vendor priority summary link
debian unimportant CVE-2017-2888 unimportant priority: Debian including 2 source packages (libsdl1.2, libsdl2), 7 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 7. https://security-tracker.debian.org/tracker/CVE-2017-2888
redhat high — https://access.redhat.com/security/cve/CVE-2017-2888
suse high CVE-2017-2888 severity important: SUSE including 33 source package names (SDL, SDL-32bit, …), 91 product×package rows across 41 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (41 product lines)): Known Not Affected 63, Fixed 28. https://www.suse.com/security/cve/CVE-2017-2888/
ubuntu medium CVE-2017-2888 medium priority: Ubuntu including 2 source packages (libsdl1.2, libsdl2), 16 status rows across 8 suites (artful, bionic, cosmic, disco, trusty, upstream, xenial, zesty): not-affected 10, released 3, ignored 2, needs-triage 1. https://ubuntu.com/security/CVE-2017-2888

Affected software / configurations for CVE-2017-2888

Vendor Product Version Raw CPE
libsdl simple_directmedia_layer 2.0.5 cpe:2.3:a:libsdl:simple_directmedia_layer:2.0.5:*:*:*:*:*:*:*
canonical ubuntu_linux 16.04 cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 18.04 cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 19.04 cpe:2.3:o:canonical:ubuntu_linux:19.04:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*

References for CVE-2017-2888

cvelogic Threat Intelligence