How severe is CVE-2023-1370?

CVE-2023-1370 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-1370?

CVE-2023-1370 affects the following packages: net.minidev:json-smart (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-1370?

Update net.minidev:json-smart to 2.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-1370 is resolved across your whole dependency graph.

How do I detect CVE-2023-1370 in my Maven dependencies?

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.

How do I mitigate CVE-2023-1370 if there is no patch (or I can't update yet)?

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.

Is CVE-2023-1370 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-1370, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-1370?

CVE-2023-1370 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-1370?

CVE-2023-1370 is classified as CWE-674 (CWE-674). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-1370 published, and has it been updated?

CVE-2023-1370 was published on March 13, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-1370 — json-smart

HIGHFix: netplex/json-smart-v2@5b3205d

CVE-2023-1370 is a high-severity (CVSS 7.5) CWE-674 vulnerability in net.minidev:json-smart. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for net.minidev:json-smart — see the affected versions and patch details below.

Stack exhaustion in json-smart leads to denial of service when parsing malformed JSON

Also known asGHSA-493p-pfq6-5258

Published

Mar 13, 2023

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-2023-1370.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

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

1 pkg affected

☕net.minidev:json-smart

Real-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

Impact

Affected versions of net.minidev:json-smart are vulnerable to Denial of Service (DoS) due to a StackOverflowError when parsing a deeply nested JSON array or object.

When reaching a ‘[‘ or ‘{‘ character in the JSON input, the code parses an array or an object respectively. It was discovered that the 3PP does not have any limit to the nesting of such arrays or objects. Since the parsing of nested arrays and objects is done recursively, nesting too many of them can cause stack exhaustion (stack overflow) and crash the software.

Patches

This vulnerability was fixed in json-smart version 2.4.9, but the maintainer recommends upgrading to 2.4.10, due to a remaining bug.

Workarounds

N/A

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.minidev:json-smart`	all versions	2.4.9`net.minidev:json-smart:2.4.9`

Affected Products

1 product · 1 configurations

Application

json-smartjson-smart_project

< 2.4.9

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

[Json-smart](https://netplex.github.io/json-smart/) is a performance foc…

research.jfrog.comNVDMar 2023

Detection & mitigation playbook

Open-source dependency

Detect
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.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-1370 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 HatImportant

Product	Fixed in	Advisory
CEQ 2.13.2-2	`json-smart`	RHSA-2023:3179
CEQ 2.7.1-1	`json-smart`	RHSA-2023:3193
OCP-Tools-4.12-RHEL-8	`jenkins-2-plugins-0:4.12.1686649756-1.el8`	RHSA-2023:3610
OCP-Tools-4.13-RHEL-8	`jenkins-0:2.401.1.1686680404-3.el8`	RHSA-2023:3622
OpenShift Developer Tools and Services for OCP 4.11	`jenkins-2-plugins-0:4.11.1686831822-1.el8`	RHSA-2023:3663
Red Hat AMQ Clients	`json-smart`	RHSA-2023:7697
Red Hat AMQ Streams 2.4.0	see advisory	RHSA-2023:3223
Red Hat AMQ Streams 2.7.0	see advisory	RHSA-2024:3527

Frequently Asked Questions

### Impact Affected versions of [net.minidev:json-smart](https://github.com/netplex/json-smart-v1) are vulnerable to Denial of Service (DoS) due to a StackOverflowError when parsing a deeply nested JSON array or object. When reaching a ‘[‘ or ‘{‘ character in the JSON input, the code parses an array or an object respectively. It was discovered that the 3PP does not have any limit to the nesting of such arrays or objects. Since the parsing of nested arrays and objects is done recursively, nesting too many of them can cause stack exhaustion (stack overflow) and crash the software. ### Patches