Skip to content

Directory Traversal in spring-boot-actuator-logview

High severity GitHub Reviewed Published Jan 4, 2021 in lukashinsch/spring-boot-actuator-logview • Updated Feb 1, 2023

Package

maven eu.hinsch:spring-boot-actuator-logview (Maven)

Affected versions

< 0.2.13

Patched versions

0.2.13

Description

Impact

The nature of this library is to expose a log file directory via admin (spring boot actuator) HTTP endpoints. Both the filename to view and a base folder (relative to the logging folder root) can be specified via request parameters. While the filename parameter was checked to prevent directory traversal exploits (so that filename=../somefile would not work), the base folder parameter was not sufficiently checked, so that filename=somefile&base=../ could access a file outside the logging base directory).

Patches

The vulnerability has been patched in release 0.2.13. Any users of 0.2.12 should be able to update without any issues as there are no other changes in that release.

Workarounds

There is no workaround to fix the vulnerability other than updating or removing the dependency. However, removing read access of the user the application is run with to any directory not required for running the application can limit the impact. Additionally, access to the logview endpoint can be limited by deploying the application behind a reverse proxy.

For more information

If you have any questions or comments about this advisory:

References

Reviewed Jan 5, 2021
Published to the GitHub Advisory Database Jan 5, 2021
Published by the National Vulnerability Database Jan 5, 2021
Last updated Feb 1, 2023

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
Low
User interaction
None
Scope
Changed
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:L/UI:N/S:C/C:H/I:N/A:N

EPSS score

93.535%
(99th percentile)

Weaknesses

CVE ID

CVE-2021-21234

GHSA ID

GHSA-p4q6-qxjx-8jgp

Source code

No known source code

Credits

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