Skip to main content
CVE-2024-28575VulnerabilityPublished Updated

CVE-2024-28575: freeimage · n/a

Affects freeimageSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 06:26 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 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 2026-10-26.

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-28575, organizations should: 1) Monitor FreeImage project updates and apply patches promptly once available. 2) Restrict local access to systems processing J2K images to trusted users only, minimizing exposure to untrusted inputs. 3) Implement input validation and sanitization for J2K images before processing with FreeImage, potentially using alternative libraries or sandboxing image processing tasks. 4) Employ application-level monitoring to detect crashes or abnormal behavior indicative of exploitation attempts. 5) Consider disabling J2K image support in FreeImage if not required, reducing the attack surface. 6) Use operating system-level protections such as address space layout randomization (ASLR) and stack canaries to mitigate buffer overflow exploitation. 7) Educate developers and system administrators about the vulnerability and safe handling of image files. These steps go beyond generic advice by focusing on local access control, input validation, and proactive monitoring tailored to the vulnerability's characteristics.

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

References

Community reviews

Loading reviews…