Spring Boot Actuator Logview
Approved changes feed: RSS · Atom
cpe:2.3:a:spring-boot-actuator-logview_project:spring-boot-actuator-logview:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Spring Boot Actuator Logview Project (d40e7a55-63cc-5293-bfc6-260d116b2f89) |
|---|---|
| Product | Spring Boot Actuator Logview (e5ff2c8d-b3e2-5524-a23d-cda1241bdb90) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/lukashinsch/spring-boot-actuator-logview |
purl2cpe | 2026-06-01 10:17:43.655266 |
pkg:maven/eu.hinsch/spring-boot-actuator-logview |
purl2cpe | 2026-06-01 10:17:43.655269 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-21234 |
vulnerable | 2026-06-08 05:29:11.436257 |
Directory Traversal
HIGH (7.7)
spring-boot-actuator-logview in a library that adds a simple logfile viewer as spring boot actuator endpoint. It is maven package "eu.hinsch:spring-boot-actuator-logview". In spring-boot-actuator-logview before version 0.2.13 there is a directory traversal vulnerability. 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). 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. 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.
Published: 2021-01-05T17:30:15.000Z
Updated: 2024-08-03T18:09:14.894Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.