Skip to content

json-smart Uncontrolled Recursion vulnerabilty

High severity GitHub Reviewed Published Mar 23, 2023 in oswaldobapvicjr/jsonmerge • Updated Jun 24, 2024

Package

maven net.minidev:json-smart (Maven)

Affected versions

< 2.4.9

Patched versions

2.4.9

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

References

Published by the National Vulnerability Database Mar 22, 2023
@oswaldobapvicjr oswaldobapvicjr published to oswaldobapvicjr/jsonmerge Mar 23, 2023
Published to the GitHub Advisory Database Mar 23, 2023
Reviewed Mar 23, 2023
Last updated Jun 24, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.122%
(48th percentile)

Weaknesses

CVE ID

CVE-2023-1370

GHSA ID

GHSA-493p-pfq6-5258

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.