LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23088: Buffer OverFlow Vulnerability in Barenboim json-parser master and v1.1.0 fixed in v1.1.1 allows an attacker...

Buffer OverFlow Vulnerability in Barenboim json-parser master and v1.1.0 fixed in v1.1.1 allows an attacker to execute arbitrary code via the json_value_parse function.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-23088 is a critical memory-safety flaw in Barenboim json-parser. The CVE says affected code in master and v1.1.0 can overflow a buffer during JSON parsing, potentially allowing arbitrary code execution. Business risk is highest where this parser handles JSON from users, APIs, or other untrusted sources.

Executive priority

Prioritize remediation for any internet-facing or partner-facing service using this parser. The potential impact is full compromise, but confirmed exposure depends on whether the library is present and reachable through untrusted JSON input.

Technical view

The issue is reported as CWE-787 out-of-bounds write in json_value_parse. CVSS 3.1 is 9.8: network-reachable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. The CVE description states it is fixed in v1.1.1.

Likely exposure

Exposure is likely limited to applications or services that embed or depend on Barenboim/json-parser master or v1.1.0. Because the CVE record lacks normalized vendor, product, and CPE data, dependency and source-code inventory are more reliable than product-name scanning.

Exploitation context

The scoring indicates remote exploitation could be possible when attacker-controlled JSON reaches the parser. The provided sources do not show CISA KEV listing, active exploitation, or a public weaponized exploit. Treat internet-facing parsers as urgent, but do not assume exploitation is occurring without additional evidence.

Researcher notes

The CVE metadata is sparse: affected vendor/product fields are n/a and only one upstream GitHub issue is listed. The strongest concrete facts are the affected versions, fixed v1.1.1, json_value_parse location, CWE-787 classification, and CVSS vector.

Mitigation direction

  • Upgrade Barenboim/json-parser usage to v1.1.1 or later where applicable.
  • Identify and replace bundled copies based on source, not only package metadata.
  • Prioritize services that parse unauthenticated or externally supplied JSON.
  • Rebuild and redeploy affected applications after dependency replacement.
  • Check the GitHub issue and CVE record for any vendor-specific guidance.

Validation and detection

  • Search SBOMs, lockfiles, and source trees for Barenboim/json-parser references.
  • Confirm no deployed service uses master or v1.1.0 code.
  • Map every untrusted JSON input path to its parser implementation.
  • Verify production builds include the upgraded parser version.
  • Document any remaining exception and its compensating controls.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2023-23088 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
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

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-23088Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-787 · source CWE mapping

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.