In Eclipse Parsson published Maven Central artifacts before version 1.1.8, the JSON parser did not enforce a default maximum on the number of characters consumed while parsing a single JSON document. Applications that parse attacker- controlled JSON can be forced to consume excessive CPU and memory by processing very large documents, including large arrays, objects, strings, numbers, whitespace, or nested structures, resulting in a denial of service. Eclipse Parsson 1.1.8 introduces a configurable maximum parsing limit with a default limit of 15 million parser-consumed characters.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
High
Complete denial of service
CVSS Vector v3.1
Weakness Type (CWE)
References 5
https://github.com/eclipse-ee4j/parsson/commit/134e8d101aa74c8b9302d0cb62f6ccb4…
emo@eclipse.org
https://github.com/eclipse-ee4j/parsson/pull/169
emo@eclipse.org
https://github.com/eclipse-ee4j/parsson/tree/1.1.8
emo@eclipse.org
https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/444
emo@eclipse.org
https://repo.maven.apache.org/maven2/org/eclipse/parsson/parsson/1.1.8/
emo@eclipse.org