Skip to content

Apache Sling Servlets Resolver executes malicious code via path traversal

High severity GitHub Reviewed Published Feb 6, 2024 to the GitHub Advisory Database • Updated Feb 14, 2024

Package

maven org.apache.sling:org.apache.sling.servlets.resolver (Maven)

Affected versions

< 2.11.0

Patched versions

2.11.0

Description

Malicious code execution via path traversal in Apache Software Foundation Apache Sling Servlets Resolver.This issue affects all version of Apache Sling Servlets Resolver before 2.11.0. However, whether a system is vulnerable to this attack depends on the exact configuration of the system.
If the system is vulnerable, a user with write access to the repository might be able to trick the Sling Servlet Resolver to load a previously uploaded script. 

Users are recommended to upgrade to version 2.11.0, which fixes this issue. It is recommended to upgrade, regardless of whether your system configuration currently allows this attack or not.

References

Published by the National Vulnerability Database Feb 6, 2024
Published to the GitHub Advisory Database Feb 6, 2024
Reviewed Feb 6, 2024
Last updated Feb 14, 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
High
Privileges required
Low
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:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.068%
(32nd percentile)

Weaknesses

CVE ID

CVE-2024-23673

GHSA ID

GHSA-h2rq-qhr7-53gm

Source code

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