Path Traversal in eu.hinsch:spring-boot-actuator-logview (CVE-2021-21234)
Summary
Path traversal in eu.hinsch:spring-boot-actuator-logview (CVE-2021-21234). Confidential information can be exposed externally. Mitigation: upgrade to 0.2.13 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-21234 has been found in eu.hinsch:spring-boot-actuator-logview.
Confidential information can be exposed externally.
What to do: upgrade eu.hinsch:spring-boot-actuator-logview to 0.2.13 or later.
If unsure, ask your IT team or search "eu.hinsch:spring-boot-actuator-logview CVE-2021-21234" on the vendor's site.
CVE-2021-21234 (eu.hinsch:spring-boot-actuator-logview) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.2.13 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in eu.hinsch:spring-boot-actuator-logview.
Check the vendor advisory for the affected versions of eu.hinsch:spring-boot-actuator-logview.
Severity: ?. Confidential information can be exposed externally.
Update to 0.2.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで eu.hinsch:spring-boot-actuator-logview を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade eu.hinsch:spring-boot-actuator-logview to 0.2.13ステージング環境で 0.2.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory search.maven.org
- patch github.com
- patch github.com