An exploitable code execution vulnerability exists in the XPM image rendering functionality of SDL2_image 2.0.4.
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.5% (FIRST EPSS); higher than 89% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: sdl2_image (Alpine:v3.10) 2.0.5-r0; libsdl2-image (Debian:12) 2.0.5+dfsg1-1; sdl-image1.2 (Debian:12) 1.2.12-12.
Low priority for now. Upgrade to sdl2_image (Alpine:v3.10) 2.0.5-r0; libsdl2-image (Debian:12) 2.0.5+dfsg1-1; sdl-image1.2 (Debian:12) 1.2.12-12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
An exploitable code execution vulnerability exists in the XPM image rendering functionality of SDL2_image 2.0.4. A specially crafted XPM image can cause an integer overflow, allocating too small of a buffer. This buffer can then be written out of bounds resulting in a heap overflow, ultimately ending in code execution. An attacker can display a specially crafted image to trigger this vulnerability.
- Published
- Jul 31, 2019
- Updated
- Jun 16, 2026
- EPSS
- 3.5% · 89th percentile
- CWE
- CWE-190
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.5%
CNA vs NVD score
- NVD
- 8.8
- CNA · talos
- 8.8
- agree
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libsdl | sdl2 image | cpe:2.3:a:libsdl:sdl2_image |
| opensuse | backports sle | cpe:2.3:a:opensuse:backports_sle |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libsdl sdl2 image2.0.4
- opensuse backports sle15.0
- opensuse leap15.0
- opensuse leap15.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (talos). Independent of NVD's CPE analysis and usually ahead of it.
n/a SDL
- SDL_image 2.0.4affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | sdl2_image | before 2.0.5-r0 | 2.0.5-r0 |
| Debian:12 | libsdl2-image | before 2.0.5+dfsg1-1 | 2.0.5+dfsg1-1 |
| Debian:12 | sdl-image1.2 | before 1.2.12-12 | 1.2.12-12 |
| openSUSE:Leap 15.0 | SDL_image | before 1.2.12+hg695-lp151.3.3.1 | 1.2.12+hg695-lp151.3.3.1 |
| openSUSE:Leap 15.0 | SDL2_image | before 2.0.5-lp151.2.5.1 | 2.0.5-lp151.2.5.1 |
| SUSE:Package Hub 15 | SDL_image | before 1.2.12+hg695-bp151.4.3.1 | 1.2.12+hg695-bp151.4.3.1 |
| SUSE:Package Hub 15 | SDL2_image | before 2.0.5-bp151.4.3.1 | 2.0.5-bp151.4.3.1 |
Same product
libsdl: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-5060An exploitable code execution vulnerability exists in the XPM image rendering function of SDL2_image 2.0.4.36Monitor
- CVE-2019-5058An exploitable code execution vulnerability exists in the XCF image rendering functionality of SDL2_image 2.0.4.36Monitor
- CVE-2019-5057An exploitable code execution vulnerability exists in the PCX image-rendering functionality of SDL2_image 2.0.4.36Monitor
- CVE-2019-5052An exploitable integer overflow vulnerability exists when loading a PCX file in SDL2_image 2.0.4.36Monitor
- CVE-2019-5051An exploitable heap-based buffer overflow vulnerability exists when loading a PCX file in SDL2_image, version 2.0.4.36Monitor
- CVE-2019-12219An issue was discovered in libSDL2.a in Simple DirectMedia Layer (SDL) 2.0.9 when used in conjunction with libSDL2_image.a in SDL2_image 2.036Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:sdl2_image | 2.0.5-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:libsdl2-image | 2.0.5+dfsg1-1 · Debian:12 | Package registry (OSV) |
| debian:sdl-image1.2 | 1.2.12-12 · Debian:12 | Package registry (OSV) |
| opensuse:SDL_image | 1.2.12+hg695-lp151.3.3.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| opensuse:SDL2_image | 2.0.5-lp151.2.5.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| suse:SDL_image | 1.2.12+hg695-bp151.4.3.1 · SUSE:Package Hub 15 | Package registry (OSV) |
| suse:SDL2_image | 2.0.5-bp151.4.3.1 · SUSE:Package Hub 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.