Skip to main content
CVE-2024-30949VulnerabilityPublished

CVE-2024-30949: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 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

AI-suggested

1. Monitor official newlib repositories and security advisories for patches addressing CVE-2024-30949 and apply them promptly once available. 2. In the interim, implement runtime protections such as stack canaries, ASLR, and DEP/NX to mitigate exploitation risks. 3. Restrict network access to devices running newlib 4.3.0 by implementing network segmentation, firewalls, and access control lists to limit exposure. 4. Conduct thorough inventory and risk assessments to identify all devices and systems using newlib 4.3.0 within the organization. 5. Employ intrusion detection and prevention systems (IDS/IPS) with updated signatures to detect potential exploitation attempts. 6. Where feasible, consider upgrading or replacing affected embedded systems with versions using patched or alternative libraries. 7. Educate development and security teams about the vulnerability to ensure secure coding and timely response to future issues. 8. Use static and dynamic analysis tools to identify similar vulnerabilities in custom or derivative codebases that incorporate newlib.

Description

An issue in newlib v.4.3.0 allows an attacker to execute arbitrary code via the time unit scaling in the _gettimeofday function.

References

Community reviews

Loading reviews…