Security readout for executives and security teams
Plain-English summary
This CVE describes a crash in ChakraCore, tied to a segmentation violation in Js::EntryPointInfo::HasInlinees(). The public record does not provide CVSS, affected product versions, or a named fix. Business urgency depends on whether your environment uses the referenced ChakraCore master build or derived code.
Executive priority
Prioritize as an exposure-confirmation task, not an emergency response, unless ChakraCore master cbb9b or derived builds process untrusted code in production. The public evidence is too incomplete to support a higher rating.
Technical view
CVE-2023-37142 concerns ChakraCore branch master cbb9b and a segmentation violation in Js::EntryPointInfo::HasInlinees(). The sources do not identify a CWE, attack vector, exploitability, affected releases, or remediation commit. Treat it as an incomplete crash-class report requiring local exposure confirmation.
Likely exposure
Likely limited to organizations using ChakraCore source from master cbb9b or downstream builds derived from it. The CVE source lists affected vendor and product as n/a, so packaged or commercial exposure cannot be confirmed from the provided evidence.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, public weaponization, or a confirmed security impact beyond segmentation violation. A crash may imply denial-of-service risk, but the sources do not prove reachability or attacker control.
Researcher notes
Key gaps are CVSS, CWE, affected release mapping, exploitability, and fix status. Focus analysis on the linked GitHub issue, the HasInlinees crash context, and whether the crash is externally reachable in downstream deployments.
Mitigation direction
- Inventory ChakraCore usage, including forks, embedded runtimes, and source builds.
- Check the GitHub issue and CVE record for upstream remediation guidance.
- Avoid exposing affected ChakraCore builds to untrusted JavaScript where practical.
- Track whether maintainers identify affected versions or a fixing commit.
Validation and detection
- Confirm whether any deployed build matches ChakraCore master cbb9b.
- Review dependency manifests, vendored source, and build provenance for ChakraCore.
- Assess whether untrusted JavaScript can reach ChakraCore in your environment.
- Document findings because public affected-version data is incomplete.
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-37142 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/6887CVE 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.