Kimageformats: Heap-buffer-overflow in readImage4v2
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=70554 ``` Crash type: Heap-buffer-overflow WRITE 1 Crash state: readImage4v2 PCXHandler::read kimgio_fuzzer.cc ```
AI Analysis
Technical Summary
The kimageformats library contains a heap-buffer-overflow vulnerability in the readImage4v2 function, specifically within the PCXHandler::read method. This was identified by OSS-Fuzz through a crash involving a heap-buffer-overflow write of size 1. The vulnerability affects numerous versions starting from 6.5.0-rc1 through 6.28.0-rc1 and later commits. No official patch or remediation details are currently available, and no known exploits in the wild have been reported.
Potential Impact
Heap-buffer-overflow vulnerabilities can lead to memory corruption, potentially allowing an attacker to cause a crash or execute arbitrary code. However, no active exploitation has been reported. The impact is considered high due to the risk of memory corruption and possible code execution if exploited.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider avoiding processing untrusted PCX image files with affected versions of kimageformats or apply any available upstream patches from the OSS-Fuzz or kimageformats maintainers.
Kimageformats: Heap-buffer-overflow in readImage4v2
Description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=70554 ``` Crash type: Heap-buffer-overflow WRITE 1 Crash state: readImage4v2 PCXHandler::read kimgio_fuzzer.cc ```
Affected software
pkg:generic/kimageformatsRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The kimageformats library contains a heap-buffer-overflow vulnerability in the readImage4v2 function, specifically within the PCXHandler::read method. This was identified by OSS-Fuzz through a crash involving a heap-buffer-overflow write of size 1. The vulnerability affects numerous versions starting from 6.5.0-rc1 through 6.28.0-rc1 and later commits. No official patch or remediation details are currently available, and no known exploits in the wild have been reported.
Potential Impact
Heap-buffer-overflow vulnerabilities can lead to memory corruption, potentially allowing an attacker to cause a crash or execute arbitrary code. However, no active exploitation has been reported. The impact is considered high due to the risk of memory corruption and possible code execution if exploited.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider avoiding processing untrusted PCX image files with affected versions of kimageformats or apply any available upstream patches from the OSS-Fuzz or kimageformats maintainers.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- OSV-2024-679
- Osv Schema Version
- 1.6.0
- Ecosystems
- ["OSS-Fuzz"]
Threat ID: 6a483ca927e9c79719d807a2
Added to database: 07/03/2026, 22:50:17 UTC
Last enriched: 08/09/2026, 18:07:44 UTC
Last updated: 09/09/2026, 15:47:13 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.