Security readout for executives and security teams
Plain-English summary
CVE-2020-23306 is a stack-overflow flaw in JerryScript 2.2.0 during regular-expression matching. Business impact depends on whether your products, firmware, or services embed JerryScript and process untrusted JavaScript or regex-related input. The public record does not provide severity scoring or a named fix.
Executive priority
Prioritize discovery first. This is not enough evidence for emergency action, but embedded runtime flaws can persist in products and firmware, so owners should confirm exposure and vendor remediation status.
Technical view
The CVE describes a stack overflow at ecma-regexp-object.c:535 in ecma_regexp_match in JerryScript 2.2.0. The source bundle does not include CVSS, CWE, affected CPEs, exploit details, or confirmed remediation version. Treat exposure as dependency-specific until vendor or project guidance is verified.
Likely exposure
Likely limited to applications, devices, firmware, or tooling that embed JerryScript 2.2.0. Exposure is higher where untrusted JavaScript or regular-expression input can reach the JerryScript engine.
Exploitation context
The supplied sources do not show active exploitation, and the CVE is not listed as KEV in the bundle. No weaponized exploit status is established from the provided evidence.
Researcher notes
Evidence is sparse: the CVE record names JerryScript 2.2.0 and a stack overflow location, but omits scoring, CWE, CPEs, and fix metadata. Avoid broad assumptions about downstream affected products without inventory or vendor confirmation.
Mitigation direction
- Inventory products and codebases for embedded JerryScript 2.2.0.
- Check JerryScript project guidance for a fixed release or patch.
- Limit untrusted JavaScript or regex input reaching affected runtimes.
- Request downstream vendor confirmation for firmware or bundled runtimes.
- Monitor crash telemetry for regex-related stack overflow symptoms.
Validation and detection
- Review SBOMs, dependency manifests, and firmware components for JerryScript 2.2.0.
- Confirm whether untrusted JavaScript can execute in affected deployments.
- Confirm whether user-controlled regex patterns reach JerryScript matching logic.
- Track the referenced JerryScript issue for remediation details.
- Document affected and unaffected products for vulnerability management.
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.
CVE-2020-23306 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/3753CVE reference · x_refsource_CONFIRM
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.