CVE-2023-51074 json
json-path Out-of-bounds Write vulnerability
published 2023-12-27 2 y ago modified 2026-09-10 1 mo ago also GHSA-pfh2-hfmq-phg5 , EUVD-2023-3260
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
json-path v2.8.0 was discovered to contain a stack overflow via the Criteria.parse() method.
Patch / fix
- maven com.jayway.jsonpath:json-path 2.9.0
- json-path jayway_jsonpath 2.9.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-51074 updated cvss 5.3
json-path: stack-based buffer overflow in Criteria.parse method
-
Red Hat OpenShift Developer Tools and Services jenkins-2-pluginsaffected: no fix planned “Will not fix”
-
Red Hat OpenShift Serverless json-path Red Hat build of Apache Camel 4 for Quarkus 3 json-pathaffected: no fix available
-
Red Hat build of OptaPlanner 8 json-pathaffected: no fix planned “Will not fix”
-
Red Hat Decision Manager 7 json-pathaffected: no fix available “Fix deferred”
-
Red Hat Fuse 7 json-path Red Hat Integration Camel Quarkus 2 json-pathaffected: no fix planned “Will not fix”
-
Red Hat OpenShift Container Platform 3.11 jenkins-2-pluginsaffected: no fix planned “Out of support scope”
-
Red Hat Process Automation 7 json-pathaffected: no fix planned “Will not fix”
-
Red Hat streams for Apache Kafka json-pathaffected: no fix available
show 5 moreshow fewer
-
Red Hat AMQ Streams 2.7.0fixed: vendor fix RHSA-2024:3527
-
Red Hat build of Apache Camel 4.4.0 for Spring Bootfixed: vendor fix RHSA-2024:2707
-
Red Hat RHBOAC camel-quarkus 3 (camel-4.0/quarkus-3.2)fixed: vendor fix RHSA-2024:0789
-
Red Hat RHINT Camel-Springboot 3.20.5fixed: vendor fix RHSA-2024:0792
-
Red Hat A-MQ Clients 2 json-path Red Hat Logging Subsystem for Red Hat OpenShift com.amazon.opendistroforelasticsearch-opendistro_security Red Hat AMQ Broker 7 json-path Red Hat AMQ Clients json-path Red Hat build of Apicurio Registry 2 json-path Red Hat build of Debezium 2 json-pathnot affected: vulnerable code not present
+11 more productsfewer
Red Hat Build of Keycloak json-path Red Hat build of Quarkus json-path Red Hat Data Grid 8 json-path Red Hat Integration Camel K 1 json-path Red Hat JBoss Data Grid 7 json-path Red Hat JBoss Enterprise Application Platform 6 json-path, org.keycloak-keycloak-parent org.keycloak-keycloak-parent Red Hat JBoss Enterprise Application Platform 7 json-path Red Hat JBoss Enterprise Application Platform 8 json-path Red Hat JBoss Enterprise Application Platform Expansion Pack json-path Red Hat Single Sign-On 7 json-path Red Hat support for Spring Boot json-path
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/json-path/JsonPath/issues/973 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.jayway.jsonpath:json-path | >=2.2.0, <2.9.0 |
2.9.0 |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/json-path/JsonPath/commit/71a09c1193726c010917f1157ecbb069ad6c3e3b
web
-
github.com
/json-path/JsonPath/issues/973
web, exploit, issue-tracking, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-51074
advisory
-
github.com
/json-path/JsonPath
package
-
github.com
/json-path/JsonPath/releases/tag/json-path-2.9.0
web
Sources
- CVE List CVE-2023-51074
- GitHub Advisory GHSA-pfh2-hfmq-phg5
- NVD CVE-2023-51074
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.