Security readout for executives and security teams
Plain-English summary
CVE-2017-14749 describes a memory corruption flaw in JerryScript 1.0. A crafted JavaScript file could crash the engine and may allow arbitrary code execution. The source bundle does not provide CVSS scoring, confirmed patches, or named downstream products.
Executive priority
Prioritize discovery first. This is old and not listed in KEV, but possible code execution raises business risk if JerryScript 1.0 is embedded in internet-facing or user-input processing systems.
Technical view
The CVE attributes the issue to incorrect null bytes in bytecode.literal data when unrecognized backslash characters are parsed, leading to heap memory corruption in jmem_heap_alloc_block_internal. Reported impacts are denial of service or possible arbitrary code execution via a crafted .js file.
Likely exposure
Exposure is likely limited to systems or products embedding JerryScript 1.0 that process untrusted JavaScript files. The provided sources do not identify affected downstream products, package names, fixed versions, or deployment environments.
Exploitation context
The CVE says remote attackers can use a crafted .js file, but the bundle provides no KEV listing and no cited evidence of active exploitation. Treat exploitability as plausible but not confirmed beyond the public issue and CVE text.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, fixed version, or downstream product list is included. The key research task is mapping embedded JerryScript usage and correlating project issue #2008 with the exact fix or release history.
Mitigation direction
- Inventory products and firmware that embed JerryScript 1.0.
- Check JerryScript project guidance and issue #2008 for fixed-version information.
- Avoid processing untrusted JavaScript with affected JerryScript builds.
- Sandbox or isolate JavaScript parsing where replacement is not immediately possible.
- Prioritize vendor-supported upgrades when a fixed build is confirmed.
Validation and detection
- Confirm whether JerryScript 1.0 exists in SBOMs, source trees, or firmware images.
- Identify services or workflows that accept user-supplied .js files.
- Review crash logs for JerryScript heap corruption signatures.
- Verify JavaScript parsing is sandboxed or disabled for untrusted input.
- Track vendor or project issue status before declaring remediation complete.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-14749 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jerryscript-project/jerryscript/issues/2008CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.