CVE-2019-5058
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn exploitable code execution vulnerability exists in the XCF image rendering functionality of SDL2_image 2.0.4. 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA heap overflow vulnerability exists in the XCF image rendering functionality of SDL2_image 2.0.4. When processing a specially crafted XCF (GIMP native image format) file, the parser fails to properly validate bounds before writing to heap memory, allowing an attacker to overwrite adjacent memory structures and achieve arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.0.4= 15.0= 15.0= 15.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SDL2_image library versionLocate the SDL2_image library (commonly libSDL2_image.so on Linux, SDL2_image.dll on Windows, or SDL2_image.framework on macOS) and query its version using tools like 'ldd -l libSDL2_image' on Linux, or check the file properties. On systems with package managers, use 'dpkg -l libsdl2-image' (Debian/Ubuntu), 'rpm -qa | grep SDL2_image' (RHEL/Fedora), or 'zypper se SDL2_image' (openSUSE).Affected if The installed version is exactly 2.0.4, or the version cannot be determined and falls within the 2.0.x lineage before 2.0.5.
-
Confirm XCF file support is presentVerify that the SDL2_image build includes XCF format support. This can be checked by examining the library's linked symbols (using 'nm -D libSDL2_image.so' on Linux or 'dumpbin /exports SDL2_image.dll' on Windows) for XCF-related functions such as 'IMG_isXCF' or 'IMG_LoadXCF_RW', or by reviewing build configuration files if source was compiled locally.Affected if XCF loading functions are present in the library and the library is in use.
-
Identify applications using SDL2_imageScan for applications that link against SDL2_image by searching for library dependencies. On Linux, use 'ldd' on binaries in common application directories, or use 'find /usr -name "*.so*" -exec ldd {} \; 2>/dev/null | grep SDL2_image'. Review application documentation or source code to determine if XCF image processing is a feature.Affected if Applications using SDL2_image are present and those applications process image files, including potentially XCF files from untrusted sources.
-
Check for XCF file processing activityIf SDL2_image with XCF support is deployed, audit any systems or applications that accept image uploads or process XCF files from external sources. Review application logs, if available, for XCF file handling code paths. Examine any custom loaders or plugins that extend SDL2_image's format support.Affected if The environment processes XCF files using applications linked against the affected SDL2_image version.
A system is affected if it runs SDL2_image version 2.0.4 and any application using that library processes XCF (GIMP native image format) files from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to SDL2_image version 2.0.5 or later which contains the fix for this vulnerability. Until an upgrade is available, ensure strict validation of XCF files from untrusted sources before processing them with applications using SDL2_image.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5058 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data