CVE-2024-28583: freeimage · n/a
Affects freeimageSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubruanxingzhi/freeimagepkg:github/ruanxingzhi/freeimageOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor official FreeImage project channels for patches or updates addressing CVE-2024-28583 and apply them promptly once available. 2. Until a patch is released, restrict local access to systems running vulnerable versions of FreeImage to trusted users only. 3. Employ application whitelisting and endpoint protection solutions to detect and prevent unauthorized code execution attempts. 4. Conduct thorough code reviews and testing of applications using FreeImage to identify and isolate usage of the readLine() function with XPM images. 5. Consider disabling or limiting support for XPM image processing in applications if feasible. 6. Implement strict access controls and segmentation to minimize the risk of local attackers gaining access to vulnerable systems. 7. Use runtime memory protection techniques such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to mitigate exploitation impact. 8. Maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.
Description
Buffer Overflow vulnerability in open source FreeImage v.3.19.0 [r1909] allows a local attacker to execute arbitrary code via the readLine() function when reading images in XPM format.