Skip to content

Path traversal vulnerability in functional web frameworks

High severity GitHub Reviewed Published Sep 13, 2024 to the GitHub Advisory Database • Updated Nov 5, 2024

Package

maven org.springframework:spring-webflux (Maven)

Affected versions

< 6.1.13

Patched versions

6.1.13
maven org.springframework:spring-webmvc (Maven)
< 6.1.13
6.1.13

Description

Applications serving static resources through the functional web frameworks WebMvc.fn or WebFlux.fn are vulnerable to path traversal attacks. An attacker can craft malicious HTTP requests and obtain any file on the file system that is also accessible to the process in which the Spring application is running.

Specifically, an application is vulnerable when both of the following are true:

  • the web application uses RouterFunctions to serve static resources
  • resource handling is explicitly configured with a FileSystemResource location

However, malicious requests are blocked and rejected when any of the following is true:

References

Published by the National Vulnerability Database Sep 13, 2024
Published to the GitHub Advisory Database Sep 13, 2024
Reviewed Sep 13, 2024
Last updated Nov 5, 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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
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:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.053%
(23rd percentile)

Weaknesses

CVE ID

CVE-2024-38816

GHSA ID

GHSA-cx7f-g6mp-7hqm

Credits

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