GHSA-v4mq-p756-p4f5
HIGHGHSA-v4mq-p756-p4f5 is a high-severity (CVSS 7.5) Path Traversal vulnerability in com.typesafe.play:play_2.12. O3 Security confirms whether GHSA-v4mq-p756-p4f5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Play Framework's Assets controller vulnerable to directory traversal
Real-World Exposure
com.typesafe.play:play_2.12Real-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
A directory traversal vulnerability has been found in the Assets controller in Play Framework 2.6.12 through 2.6.15 (fixed in 2.6.16) when running on Windows. It allows a remote attacker to download arbitrary files from the target server via specially crafted HTTP requests.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.typesafe.play:play_2.12 | ≥ 2.6.12&&< 2.6.16 | 2.6.16 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.typesafe.play:play_2.12. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.typesafe.play:play_2.12 to 2.6.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v4mq-p756-p4f5 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 pinpoints whether GHSA-v4mq-p756-p4f5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-v4mq-p756-p4f5. 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-v4mq-p756-p4f5 in your dependencies?
O3 detects GHSA-v4mq-p756-p4f5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.