CVE-2024-47855VulnerabilityPublished 4 Oct 2024Updated 7 Nov 2024

CVE-2024-47855: json-lib · n/a

Affects json-libSource CVE Database V5

Not known to be exploited · 17% EPSS · CVSS 5.3 Medium : upgrade to 3.1.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 17.5% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.1.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade net.sf.json-lib/json-lib to 3.1.0.

Affected software

Product	Affected	Fixed in
Mavennet.sf.json-lib/json-lib`pkg:maven/net.sf.json-lib/json-lib`Other threats	Affected <3.1.0	Fixed in 3.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-47855, organizations should: 1) Upgrade JSON-lib to version 3.1.0 or later once the patch is officially released to ensure the vulnerability is addressed. 2) Implement strict input validation and sanitization on all JSON inputs, especially those containing comments, to detect and reject malformed or unbalanced comment strings before parsing. 3) Employ runtime monitoring and anomaly detection to identify unusual resource consumption or application crashes related to JSON parsing. 4) Use application-layer firewalls or API gateways to filter and block suspicious JSON payloads from untrusted sources. 5) Conduct thorough testing of JSON parsing components under malformed input scenarios to verify robustness. 6) Maintain up-to-date inventory of software dependencies to quickly identify and remediate vulnerable library versions. These steps go beyond generic advice by focusing on proactive input validation and layered defenses to reduce exposure until patches are applied.

Description

util/JSONTokener.java in JSON-lib before 3.1.0 mishandles an unbalanced comment string.

Impact

The primary impact of CVE-2024-47855 is denial of service, which can disrupt application availability and potentially cause service outages. Organizations relying on JSON-lib for JSON parsing in Java applications, particularly those exposed to external or untrusted inputs, risk application crashes or degraded performance. This can affect web services, APIs, and backend systems that process JSON data. While the vulnerability does not compromise data confidentiality or integrity, the availability impact can lead to operational downtime, loss of customer trust, and potential financial losses. Systems with high availability requirements or critical infrastructure components using affected versions are particularly vulnerable to service interruptions. Since exploitation requires no authentication or user interaction, attackers can remotely trigger the issue, increasing the risk of automated or large-scale attacks.

References

Community reviews

Loading reviews…