Skip to content

Apache Sling Commons JSON bundle vulnerable to Improper Input Validation

Critical severity GitHub Reviewed Published May 15, 2023 to the GitHub Advisory Database • Updated Mar 29, 2024

Package

maven org.apache.sling:org.apache.sling.commons.json (Maven)

Affected versions

<= 2.0.20

Patched versions

None

Description

Improper input validation in the Apache Sling Commons JSON bundle allows an attacker to trigger unexpected errors by supplying specially-crafted input.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer. The org.apache.sling.commons.json bundle has been deprecated as of March 2017 and should not be used anymore. Consumers are encouraged to consider the Apache Sling Commons Johnzon OSGi bundle provided by the Apache Sling project, but may of course use other JSON libraries.

References

Published by the National Vulnerability Database May 15, 2023
Published to the GitHub Advisory Database May 15, 2023
Reviewed May 15, 2023
Last updated Mar 29, 2024

Severity

Critical

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
High
Integrity
High
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:H/I:H/A:H

EPSS score

0.659%
(80th percentile)

Weaknesses

CVE ID

CVE-2022-47937

GHSA ID

GHSA-8j28-34qq-gmch

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.