Skip to main content
VulnerabilityPublished Updated

CVE-2024-28572: freeimage · Buffer Overflow

Affects freeimageSource CVE Database V5

0

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubruanxingzhi/freeimagepkg:github/ruanxingzhi/freeimageOther threatsAffected
  • =3.19.0
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-28572, organizations should monitor for official patches or updates from the FreeImage project and apply them promptly once released. In the absence of patches, restricting local access to systems running FreeImage-based applications is critical to reduce the risk of exploitation. Employing application whitelisting and limiting user privileges can help prevent unauthorized local code execution. Additionally, sandboxing or containerizing applications that use FreeImage can contain potential crashes and minimize impact. Developers should review and update their use of FreeImage, potentially replacing or wrapping the vulnerable function with safer alternatives. Implementing robust input validation and fuzz testing on JPEG image inputs can help detect and prevent similar vulnerabilities. Regularly auditing software dependencies and maintaining an inventory of applications using FreeImage will aid in targeted mitigation efforts.

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 FreeImage_SetTagValue() function when reading images in JPEG format.

References

Community reviews

Loading reviews…