Skip to main content
VulnerabilityPublished Updated

CVE-2024-28573: vul-report · Buffer Overflow

Affects vul-reportSource CVE Database V5

0

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 09:15 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 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/vul-reportpkg:github/ruanxingzhi/vul-reportOther 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-28573, organizations should first monitor for updates or patches from the FreeImage project and apply them promptly once available. Until a patch is released, consider the following specific actions: 1) Restrict local user permissions to limit who can supply or process JPEG images using FreeImage-based applications. 2) Implement input validation or filtering to detect and block suspicious or malformed JPEG files before processing. 3) Use application sandboxing or process isolation to contain potential crashes and prevent system-wide impact. 4) Employ runtime protections such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to reduce exploitation success. 5) Audit and review software dependencies to identify and replace FreeImage usage with alternative libraries if feasible. 6) Educate users about the risks of opening untrusted image files locally. These targeted mitigations go beyond generic advice by focusing on controlling local file inputs and isolating vulnerable components.

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

References

Community reviews

Loading reviews…