CVE-2023-47995
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 · uneditedMemory Allocation with Excessive Size Value discovered in BitmapAccess.cpp::FreeImage_AllocateBitmap in FreeImage 3.18.0 allows attackers to cause a denial of service.
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 confidenceA memory allocation vulnerability exists in FreeImage_AllocateBitmap function in BitmapAccess.cpp of FreeImage 3.18.0 where the library allocates memory based on values that can be manipulated to request excessive sizes, potentially causing resource exhaustion and denial of service.
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.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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 FreeImage library presenceSearch for FreeImage DLL files (FreeImage.dll, libfreeimage.so) or static libraries in the system or application dependenciesAffected if FreeImage library files are found in the environment
-
Determine FreeImage versionCheck the version metadata of the FreeImage library file, or inspect version strings in the compiled binary, or run: strings <library_file> | grep -i 'freeimage.*3\.18\.0'Affected if Version is exactly 3.18.0
-
Identify usage of FreeImage_AllocateBitmapSearch application binaries or source code for calls to FreeImage_AllocateBitmap function (e.g., grep -r 'FreeImage_AllocateBitmap' or inspect import tables)Affected if Code calls FreeImage_AllocateBitmap to allocate bitmaps
-
Check for input validation on bitmap dimensionsInspect source code or binary for validation logic on width/height parameters passed to FreeImage_AllocateBitmap before the callAffected if No bounds checking exists on bitmap dimensions before the allocation call
Environment is affected if FreeImage version 3.18.0 is in use and code calls FreeImage_AllocateBitmap without validating that width/height parameters are within safe limits.
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.
dbcve · scopedUpgrade to a patched version of FreeImage that implements proper bounds validation on memory allocation sizes, or if no patch is available, implement input validation on image dimensions before calling FreeImage_AllocateBitmap.
FreeImage version newer than 3.18.0 (check official releases for 3.19.0 or later)
- 1. Identify all systems and applications that use FreeImage version 3.18.0
- 2. Check FreeImage's official GitHub repository (github.com) for newer releases beyond version 3.18.0
- 3. Download and test the latest stable FreeImage release in a non-production environment
- 4. Verify the fix addresses the BitmapAccess.cpp::FreeImage_AllocateBitmap vulnerability
- 5. Deploy the upgraded FreeImage library to production systems
- 6. Monitor for any application compatibility issues after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47995 — 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-2023-47995 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