CVE-2024-31570
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 · uneditedlibfreeimage in FreeImage 3.4.0 through 3.18.0 has a stack-based buffer overflow in the PluginXPM.cpp Load function via an XPM file.
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 · moderate confidenceStack-based buffer overflow in FreeImage's PluginXPM.cpp Load function when processing XPM (X PixMap) image files. The vulnerability results from insufficient bounds checking during XPM file parsing, allowing an attacker to overwrite stack memory by supplying a specially crafted XPM file with oversized image dimensions or color data.
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>= 3.4.0, <= 3.18.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 installed FreeImage versionSearch for libfreeimage or freeimage library files on the system and query their version metadata using tools like 'strings', 'file', or package managers (dpkg, rpm, brew). Compare the version against the affected range: 3.4.0 through 3.18.0.Affected if The installed version falls within >= 3.4.0 and <= 3.18.0
-
Locate PluginXPM.cpp or XPM plugin componentSearch for files named PluginXPM.cpp, PluginXPM, or XPM-related plugin binaries within the FreeImage installation directory or source tree.Affected if The vulnerable XPM parsing code exists in the installed FreeImage version
-
Confirm XPM file processing capabilityCheck if applications or services using libfreeimage have the XPM decoder enabled or loaded. This may involve inspecting application configuration, runtime plugin directories, or testing XPM file loading capabilities.Affected if XPM file processing is enabled and the FreeImage version is within the affected range
-
Audit for XPM file input handlingReview logs, file processing pipelines, or application behavior for evidence of XPM (image/x-xpixmap MIME type) file parsing. Check if user-supplied or network-received XPM files are processed by FreeImage.Affected if XPM files are being processed by a vulnerable FreeImage version
A user is affected if FreeImage version 3.4.0 through 3.18.0 is installed AND XPM image files are processed by an application using this library.
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 dataUpdate FreeImage to a patched version if available; otherwise, restrict or disable XPM file processing in applications using libfreeimage until a fix can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31570 — 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-2024-31570 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