CVE-2024-28571: freeimage · n/a
Affects freeimageSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% 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:N/I:N/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-25.
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
To mitigate CVE-2024-28571, organizations should first identify all software and systems using FreeImage version 3.19.0 [r1909], especially those processing JPEG images locally. Until an official patch is released, consider the following specific actions: 1) Restrict local access to trusted users only, minimizing the risk of local exploitation. 2) Implement strict input validation and sanitization on JPEG files before they are processed by FreeImage, potentially using alternative image validation tools or libraries to filter out malformed images. 3) Monitor application logs and system stability for signs of crashes or abnormal behavior related to image processing. 4) Where feasible, isolate image processing components in sandboxed or containerized environments to limit the impact of a crash. 5) Stay updated with FreeImage project announcements and apply patches promptly once available. 6) Consider upgrading to a later, unaffected version of FreeImage if available or replacing FreeImage with alternative libraries that do not exhibit this vulnerability. 7) For embedded devices, coordinate with vendors for firmware updates addressing this issue.
Description
Buffer Overflow vulnerability in open source FreeImage v.3.19.0 [r1909] allows a local attacker to cause a denial of service (DoS) via the fill_input_buffer() function when reading images in JPEG format.