GHSA-hcwx-7q5v-vc67 — dependency-check-maven
HIGHGHSA-hcwx-7q5v-vc67 is a high-severity (CVSS 7.8) Path Traversal vulnerability in org.owasp:dependency-check-maven. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.owasp:dependency-check-maven — see the affected versions and patch details below.
Path Traversal in OWASP Dependency-Check
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-hcwx-7q5v-vc67 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.owasp:dependency-check-mavenReal-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
OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitrary files via a crafted archive that holds directory traversal filenames.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.owasp:dependency-check-maven | all versions | 3.2.0org.owasp:dependency-check-maven:3.2.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp:dependency-check-maven, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.owasp:dependency-check-maven to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hcwx-7q5v-vc67 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hcwx-7q5v-vc67 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-hcwx-7q5v-vc67. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hcwx-7q5v-vc67 in your dependencies?
O3 Security finds GHSA-hcwx-7q5v-vc67 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.