Security readout for executives and security teams
Plain-English summary
CVE-2023-37139 reports a stack overflow in ChakraCore source branch master cbb9b. The public metadata does not identify supported affected products, versions, severity, business impact, or a named fix. Treat this as an exposure-identification item unless your environment builds or embeds ChakraCore from the affected source.
Executive priority
Investigate only if ChakraCore is present in your software estate. With no severity, affected release, active exploitation, or fix evidence in the sources, this should not outrank known exploited or business-critical vulnerabilities.
Technical view
The CVE describes a stack overflow in Js::ScopeSlots::IsDebuggerScopeSlotArray() in ChakraCore master cbb9b. The supplied sources provide no CVSS score, CWE, CPE, affected release list, exploitability details, or remediation version. Impact cannot be determined from the available evidence.
Likely exposure
Exposure is unclear from the CVE record. Organizations most likely to care are those compiling, embedding, or maintaining forks of ChakraCore around the cited master cbb9b source state.
Exploitation context
The source bundle does not show CISA KEV listing, public exploitation, exploit maturity, or exploitation prerequisites. Do not assume active exploitation from the available evidence.
Researcher notes
The CVE record is sparse: one GitHub issue reference, no CVSS, no CWE, no CPEs, affected vendor/product marked n/a, and KEV is false. Any deeper assessment requires reviewing upstream issue details and local ChakraCore usage evidence.
Mitigation direction
- Check ChakraCore upstream guidance and the referenced GitHub issue for fix status.
- Inventory applications, forks, and embedded runtimes that include ChakraCore.
- Avoid deploying unreviewed builds from the cited master source state.
- Track vendor or maintainer updates before claiming remediation.
- Document temporary risk acceptance if no affected usage is found.
Validation and detection
- Search SBOMs and build manifests for ChakraCore usage.
- Confirm whether any production system embeds ChakraCore from source.
- Compare internal fork history against master cbb9b where possible.
- Review the referenced issue for maintainer discussion and closure status.
- Record evidence when ChakraCore is absent from runtime and build paths.
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-2023-37139 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/chakra-core/ChakraCore/issues/6884CVE reference
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.