Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Eclipse Foundation Eclipse Parsson
Default version status: unaffected
1.0.0 to ≤ 1.1.7affected
References
- https://github.com/eclipse-ee4j/parsson/commit/134e8d101aa74c8b9302d0cb62f6ccb4912a9d0c ↗
- https://github.com/eclipse-ee4j/parsson/pull/169 ↗
- https://repo.maven.apache.org/maven2/org/eclipse/parsson/parsson/1.1.8/ ↗
- https://github.com/eclipse-ee4j/parsson/tree/1.1.8 ↗
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/444 ↗