CVE-2024-57699 — json-smart
HIGHCVE-2024-57699 is a high-severity (CVSS 7.5) CWE-674 vulnerability in net.minidev:json-smart. A fix is available for net.minidev:json-smart — see the affected versions and patch details below.
Netplex Json-smart Uncontrolled Recursion vulnerability
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-57699.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-57699 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
net.minidev:json-smartReal-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
A security issue was found in Netplex Json-smart 2.5.0 through 2.5.1. When loading a specially crafted JSON input, containing a large number of ’{’, a stack exhaustion can be trigger, which could allow an attacker to cause a Denial of Service (DoS). This issue exists because of an incomplete fix for CVE-2023-1370.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.minidev:json-smart | ≥ 2.5.0&&< 2.5.2 | 2.5.2net.minidev:json-smart:2.5.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.minidev:json-smart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.minidev:json-smart to 2.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-57699 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-57699 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-57699. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
This issue exists because of an incomplete fix for CVE-2023-1370, therefore it only affects json-smart v2.5.0 through v2.5.1 (inclusive).
| Product | Fixed in | Advisory |
|---|---|---|
| HawtIO HawtIO 4.2.0 | json-smart | RHSA-2025:8761 |
| OCP-Tools-4.12-RHEL-8 | jenkins-0:2.504.2.1750932984-3.el8 | RHSA-2025:10118 |
| OCP-Tools-4.13-RHEL-8 | jenkins-0:2.504.2.1750916374-3.el8 | RHSA-2025:10119 |
| OCP-Tools-4.14-RHEL-8 | jenkins-0:2.504.2.1750903189-3.el8 | RHSA-2025:10120 |
| OCP-Tools-4.15-RHEL-8 | jenkins-0:2.504.2.1750856366-3.el8 | RHSA-2025:10104 |
| OCP-Tools-4.16-RHEL-9 | jenkins-0:2.504.2.1750857144-3.el9 | RHSA-2025:10098 |
| OCP-Tools-4.17-RHEL-9 | jenkins-0:2.504.2.1750851690-3.el9 | RHSA-2025:10097 |
| OCP-Tools-4.18-RHEL-9 | jenkins-0:2.504.2.1750846524-3.el9 | RHSA-2025:10092 |
Frequently Asked Questions
Is CVE-2024-57699 in your dependencies?
O3 Security finds CVE-2024-57699 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.