Skip to content

Withdrawn: CVE Rejected: JXPath vulnerable to remote code execution when interpreting untrusted XPath expressions

Critical severity GitHub Reviewed Published Oct 6, 2022 to the GitHub Advisory Database • Updated Mar 6, 2023
Withdrawn This advisory was withdrawn on Mar 6, 2023

Package

maven commons-jxpath:commons-jxpath (Maven)

Affected versions

<= 1.3

Patched versions

None

Description

This advisory has been withdrawn due to the CVE being rejected.

Original advisory text

Those using JXPath to interpret untrusted XPath expressions may be vulnerable to a remote code execution attack. All JXPathContext class functions processing a XPath string are vulnerable except compile() and compilePath() function. The XPath expression can be used by an attacker to load any Java class from the classpath resulting in code execution.

References

Published by the National Vulnerability Database Oct 6, 2022
Published to the GitHub Advisory Database Oct 6, 2022
Reviewed Oct 6, 2022
Withdrawn Mar 6, 2023
Last updated Mar 6, 2023

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

Weaknesses

CVE ID

CVE-2022-41852

GHSA ID

GHSA-wrx5-rp7m-mm49

Source code

Credits

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