LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24345: JerryScript through 2.3.0 allows stack consumption via function a(){new new Proxy(a,{})}JSON.parse("[]",a).

JerryScript through 2.3.0 allows stack consumption via function a(){new new Proxy(a,{})}JSON.parse("[]",a). NOTE: the vendor states that the problem is the lack of the --stack-limit option

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-24345 is a stack-consumption denial-of-service issue in JerryScript through 2.3.0. A crafted JavaScript pattern can exhaust stack resources and crash or disrupt the embedded JavaScript engine. The source bundle does not provide a CVSS score, affected CPEs, or a named patch.

Executive priority

Prioritize assessment if JerryScript is embedded in exposed products, devices, or services that process untrusted scripts. Business impact appears limited to denial of service based on current evidence, but metadata is incomplete, so asset discovery and vendor guidance should drive urgency.

Technical view

The CVE describes stack consumption in JerryScript through 2.3.0 involving recursive object construction during JSON parsing. The vendor note says the underlying problem is absence of the --stack-limit option. Structured vulnerability metadata is incomplete: no CVSS, CWE, CPE, or formal fixed-version details are provided in the bundle.

Likely exposure

Exposure is most likely in products, firmware, or services embedding JerryScript through 2.3.0, especially where untrusted JavaScript or JSON parsing callbacks can execute and stack limits are not configured. Structured affected-product data is not available in the CVE bundle.

Exploitation context

The source bundle includes a public GitHub issue reference and the CVE description contains a triggering pattern, but there is no KEV listing and no cited evidence of active exploitation. Treat this as a potential denial-of-service risk, not proven in-the-wild exploitation.

Researcher notes

The primary uncertainty is incomplete CVE metadata. The description identifies JerryScript through 2.3.0 and a vendor note about --stack-limit, but does not provide CVSS, CWE, CPEs, or confirmed fixed release details. Avoid assuming broader product exposure without an SBOM or source review.

Mitigation direction

  • Inventory embedded JerryScript versions and identify deployments through 2.3.0.
  • Check JerryScript vendor guidance and linked issue before choosing upgrade or backport actions.
  • Enable or enforce --stack-limit where applicable, matching the vendor note.
  • Reduce exposure to untrusted JavaScript inputs in affected embedded environments.
  • Monitor affected services or devices for crashes consistent with stack exhaustion.

Validation and detection

  • Confirm whether JerryScript is present in the product or firmware bill of materials.
  • Verify the exact JerryScript version and build configuration.
  • Check whether --stack-limit is available and enabled in affected builds.
  • Review whether untrusted JavaScript or parser callbacks can reach the engine.
  • Correlate crash telemetry with stack exhaustion or recursive parsing behavior.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2020-24345 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.