Skip to main content
VulnerabilityPublished Updated

CVE-2024-24258: freeglut · Memory Leak

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Feb 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
GitHubfreeglut/freeglutpkg:github/freeglut/freeglutOther threatsAffected
  • =3.4.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. Monitor official freeglut repositories and security advisories closely for patches addressing CVE-2024-24258 and apply them promptly upon release.
  2. Conduct an inventory of all software and systems using freeglut 3.4.0 to identify vulnerable instances.
  3. Limit network exposure of applications using freeglut where possible, employing network segmentation and firewall rules to restrict access to trusted users and systems.
  4. Implement resource monitoring on affected systems to detect abnormal memory consumption patterns indicative of exploitation attempts.
  5. Where feasible, consider upgrading to alternative libraries or versions not affected by this vulnerability until an official patch is available.
  6. Employ application-level mitigations such as input validation or usage restrictions on the glutAddSubMenu function if source code access and modification are possible.
  7. Educate development and operations teams about the vulnerability to ensure rapid response and awareness.
  8. Prepare incident response plans that include steps for memory leak exploitation scenarios to minimize downtime.

Description

freeglut 3.4.0 was discovered to contain a memory leak via the menuEntry variable in the glutAddSubMenu function.

References

Community reviews

Loading reviews…