CVE-2018-3977

Exp

An exploitable code execution vulnerability exists in the XCF image rendering functionality of SDL2_image-2.0.3. A specially crafted XCF image can cause a heap overflow, resulting in code execution. An attacker can display a specially crafted image to trigger this vulnerability.

Published: 2018-11-01 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-3977 is rated High Exploit Risk (83.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 3.48%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +2.54% 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-2018-3977

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

Exploit prediction scoring system (EPSS) score for CVE-2018-3977

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.94% 3.48% +2.54%
2 2025-12-17 0.80% 0.94% +0.14%
3 2025-11-21 — 0.80% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-3977

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
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]
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-2018-3977

OS Trackers for CVE-2018-3977

vendor priority summary link
debian not yet assigned CVE-2018-3977 not yet assigned priority: Debian including 2 source packages (libsdl2-image, sdl-image1.2), 10 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 10. https://security-tracker.debian.org/tracker/CVE-2018-3977
gentoo normal CVE-2018-3977: 1 GLSA(s) (201903-17), 1 atom(s) (media-libs/sdl2-image); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2018-3977
suse high CVE-2018-3977 severity important: SUSE including 15 source package names (SDL_image-1.2.6-84.46.1, SDL_image-devel-1.2.6-84.46.1, …), 15 product×package rows across 5 product lines (SUSE Linux Enterprise Software Development Kit 11 SP4, SUSE Package Hub 15, … (5 product lines)): Fixed 15. https://www.suse.com/security/cve/CVE-2018-3977/
ubuntu medium CVE-2018-3977 medium priority: Ubuntu including 2 source packages (libsdl2-image, sdl-image1.2), 24 status rows across 12 suites (bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, trusty, upstream, xenial): not-affected 17, released 6, ignored 1. https://ubuntu.com/security/CVE-2018-3977

Affected software / configurations for CVE-2018-3977

Vendor Product Version Raw CPE
libsdl sdl_image 2.0.3 cpe:2.3:a:libsdl:sdl_image:2.0.3:*:*:*:*:*:*:*

References for CVE-2018-3977

cvelogic Threat Intelligence