How severe is GHSA-p4q6-qxjx-8jgp?

GHSA-p4q6-qxjx-8jgp has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-p4q6-qxjx-8jgp?

GHSA-p4q6-qxjx-8jgp affects the following packages: eu.hinsch:spring-boot-actuator-logview (Maven). Ecosystems affected: Maven.

How do I fix GHSA-p4q6-qxjx-8jgp?

Update eu.hinsch:spring-boot-actuator-logview to version 0.2.13 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-p4q6-qxjx-8jgp actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-p4q6-qxjx-8jgp, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-p4q6-qxjx-8jgp?

GHSA-p4q6-qxjx-8jgp has an EPSS (Exploit Prediction Scoring System) score of 93.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-p4q6-qxjx-8jgp?

GHSA-p4q6-qxjx-8jgp is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-p4q6-qxjx-8jgp?

A Nuclei detection template exists for GHSA-p4q6-qxjx-8jgp, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-p4q6-qxjx-8jgp published, and has it been updated?

GHSA-p4q6-qxjx-8jgp was published on January 5, 2021 and was last updated on March 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-p4q6-qxjx-8jgp

HIGH

Directory Traversal in spring-boot-actuator-logview

Also known asCVE-2021-21234

Published

Jan 5, 2021

Updated

Mar 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

93.7%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕eu.hinsch:spring-boot-actuator-logview

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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:

Open an issue in the github repo

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`eu.hinsch:spring-boot-actuator-logview`	all versions	0.2.13

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

spring-boot-actuator-logview in a library that adds a simple logfile vie…

github.comGithubOct 2021

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-p4q6-qxjx-8jgp in your stack?

O3 detects GHSA-p4q6-qxjx-8jgp across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works