Skip to content

StaticHandler disclosure of classpath resources on Windows when mounted on a wildcard route

Moderate severity GitHub Reviewed Published Feb 9, 2023 in vert-x3/vertx-web • Updated Dec 20, 2023

Package

maven io.vertx:vertx-web (Maven)

Affected versions

>= 4.0.0, < 4.3.8

Patched versions

4.3.8

Description

Summary

When running vertx web applications that serve files using StaticHandler on Windows Operating Systems and Windows File Systems, if the mount point is a wildcard (*) then an attacker can exfiltrate any class path resource.

Details

When computing the relative path to locate the resource, in case of wildcards, the code:

https://github.com/vert-x3/vertx-web/blob/62c0d66fa1c179ae6a4d57344631679a2b97e60f/vertx-web/src/main/java/io/vertx/ext/web/impl/Utils.java#L83

returns the user input (without validation) as the segment to lookup. Even though checks are performed to avoid escaping the sandbox, given that the input was not sanitized \ are not properly handled and an attacker can build a path that is valid within the classpath.

PoC

https://github.com/adrien-aubert-drovio/vertx-statichandler-windows-traversal-path-vulnerability

References

@vietj vietj published to vert-x3/vertx-web Feb 9, 2023
Published by the National Vulnerability Database Feb 9, 2023
Published to the GitHub Advisory Database Feb 10, 2023
Reviewed Feb 10, 2023
Last updated Dec 20, 2023

Severity

Moderate

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.152%
(52nd percentile)

Weaknesses

CVE ID

CVE-2023-24815

GHSA ID

GHSA-53jx-vvf9-4x38

Source code

Credits

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