Security readout for executives and security teams
Plain-English summary
CVE-2023-23086 is a critical buffer overflow reported in MojoJson v1.2.3. The record says the flaw is in SkipString and may allow arbitrary code execution. Business risk is highest where MojoJson parses JSON supplied by internet users, APIs, partners, or files from untrusted sources.
Executive priority
Treat as urgent for any internet-facing or partner-facing service using MojoJson v1.2.3. If the library is absent or only parses trusted internal data, urgency drops. The immediate executive ask is asset confirmation and exposure reduction, not blind emergency patching without vendor guidance.
Technical view
The CVE describes a CWE-787 out-of-bounds write in MojoJson v1.2.3 SkipString. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. The source bundle does not identify CPEs, downstream products, a fixed version, or confirmed exploitation.
Likely exposure
Exposure is likely limited to applications that embed or package MojoJson v1.2.3 and process attacker-controlled JSON. The CVE record lists vendor and product as n/a, so affected asset discovery may require source, dependency, SBOM, and binary review rather than CPE matching.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. However, the CVSS vector indicates a potentially remote, unauthenticated, no-interaction condition if the vulnerable parser is reachable through untrusted JSON input. Evidence is insufficient to describe real-world exploit prevalence.
Researcher notes
The public record is sparse: one GitHub issue reference, CVSS 9.8, CWE-787, and no structured affected CPEs. Avoid overclaiming exploitation or fixed versions. Validation should focus on dependency provenance, parser reachability, and whether attacker-controlled JSON reaches SkipString-like string parsing paths.
Mitigation direction
- Inventory all applications and dependencies for MojoJson v1.2.3 usage.
- Track the CVE record and upstream GitHub issue for official maintainer guidance.
- Reduce exposure where MojoJson parses untrusted JSON from network or file inputs.
- Prioritize replacement or upgrade only when a validated safe version or alternative is confirmed.
- Add monitoring around crashes or abnormal behavior in services parsing JSON.
Validation and detection
- Search source trees, lockfiles, vendored code, and SBOMs for MojoJson v1.2.3.
- Identify code paths where MojoJson parses external, user, partner, or API-supplied JSON.
- Confirm whether exposed services can receive untrusted JSON before authentication.
- Check whether the deployed parser version differs from repository or build metadata.
- Document findings because CPE-based scanner coverage may be 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.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution 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-2023-23086 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/scottcgi/MojoJson/issues/2CVE 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.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.