Skip to main content
VulnerabilityPublished Updated

CVE-2024-29489: jerryscript · NULL Pointer Dereference

Affects jerryscriptSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 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
GitHubjerryscript-project/jerryscriptpkg:github/jerryscript-project/jerryscriptOther threatsAffected
  • =2.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 Jerryscript repositories and security advisories for patches or updates addressing CVE-2024-29489 and apply them promptly once available.
  2. Restrict local access to devices running Jerryscript to trusted users only, minimizing the risk of local exploitation.
  3. Implement strict input validation and sanitization on any JavaScript code or data processed by Jerryscript to prevent malformed inputs that could trigger the null pointer dereference.
  4. Employ runtime monitoring and watchdog mechanisms to detect and recover from crashes caused by this vulnerability, ensuring system availability.
  5. For critical systems, consider isolating Jerryscript execution environments or using alternative JavaScript engines with no known vulnerabilities.
  6. Conduct security testing and fuzzing on Jerryscript integrations to identify and mitigate similar stability issues proactively.
  7. Educate local users and administrators about the risk and the need to avoid executing untrusted scripts or code on affected devices.

Description

Jerryscript 2.4.0 has SEGV at ./jerry-core/ecma/base/ecma-helpers.c:238:58 in ecma_get_object_type.

References

Community reviews

Loading reviews…