CVE-2023-51074 is a medium-severity (CVSS 5.3) remote code execution vulnerability in com.jayway.jsonpath:json-path. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.jayway.jsonpath:json-path — see the affected versions and patch details below.
json-path Out-of-bounds Write vulnerability
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.jayway.jsonpath:json-pathReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
json-path v2.8.0 was discovered to contain a stack overflow via the Criteria.parse() method.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.jayway.jsonpath:json-path | ≥ 2.2.0&&< 2.9.0 | 2.9.0com.jayway.jsonpath:json-path:2.9.0 |
Affected Products
jayway jsonpathjson-pathResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.jayway.jsonpath:json-path, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.jayway.jsonpath:json-path to 2.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-51074 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat rates this at maximum of a Moderate impact. When interacting with a server to explore this possible vulnerability, the attacker would be the only one seeing a HTTP 500 error and no other user (or the server entirely) would be vulnerable in a real application scenario with multi-threads.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat AMQ Streams 2.7.0 | see advisory | RHSA-2024:3527 |
| Red Hat build of Apache Camel 4.4.0 for Spring Boot | json-path | RHSA-2024:2707 |
| RHBOAC camel-quarkus 3 (camel-4.0/quarkus-3.2) | json-path | RHSA-2024:0789 |
| RHINT Camel-Springboot 3.20.5 | json-path | RHSA-2024:0792 |
Frequently Asked Questions
Is CVE-2023-51074 in your dependencies?
Find it across Maven, including transitive dependencies.