Skip to main content
CVE-2024-28568VulnerabilityPublished Updated

CVE-2024-28568: freeimage · n/a

Affects freeimageSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% 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

1. Restrict local access to systems running FreeImage 3.19.0, ensuring only trusted users have login capabilities. 2. Monitor applications using FreeImage for unexpected crashes or abnormal behavior when processing TIFF images, especially those containing IPTC metadata. 3. Implement application-level sandboxing or process isolation to contain potential crashes and prevent cascading failures. 4. Employ intrusion detection systems to identify anomalous local activity that could indicate exploitation attempts. 5. Regularly review and update software dependencies; apply patches or upgrade FreeImage to a fixed version once available from the maintainers. 6. If immediate patching is not possible, consider disabling or restricting processing of TIFF images with IPTC profiles as a temporary workaround. 7. Conduct code audits or fuzz testing on image processing components to identify similar vulnerabilities proactively. 8. Educate system administrators and developers about the vulnerability and encourage secure coding and handling of untrusted image inputs.

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

References

Community reviews

Loading reviews…