GHSA-j6qj-j888-vvgq
LOWGHSA-j6qj-j888-vvgq is a low-severity (CVSS 2.7) Information Exposure vulnerability in org.eclipse.jetty:jetty-deploy. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-j6qj-j888-vvgq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Directory exposure in jetty
Real-World Exposure
org.eclipse.jetty:jetty-deploy☕org.eclipse.jetty:jetty-deploy☕org.eclipse.jetty:jetty-deployReal-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
If the ${jetty.base} directory or the ${jetty.base}/webapps directory is a symlink (soft link in Linux), the contents of the ${jetty.base}/webapps directory may be deployed as a static web application, exposing the content of the directory for download.
For example, the problem manifests in the following ${jetty.base}:
demo-base/
├── etc
├── lib
├── resources
├── start.d
├── deploy
│ └── async-rest.war
└── webapps -> deploy
Workarounds
Do not use a symlink
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jetty:jetty-deploy | ≥ 9.4.32&&< 9.4.39 | 9.4.39 |
| ☕Maven | org.eclipse.jetty:jetty-deploy | ≥ 10.0.0&&< 10.0.2 | 10.0.2 |
| ☕Maven | org.eclipse.jetty:jetty-deploy | ≥ 11.0.0&&< 11.0.2 | 11.0.2 |
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.eclipse.jetty:jetty-deploy. 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 org.eclipse.jetty:jetty-deploy to 9.4.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j6qj-j888-vvgq 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-j6qj-j888-vvgq 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-j6qj-j888-vvgq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
In OpenShift Container Platform (OCP), the hive/presto/hadoop components that comprise the OCP metering stack, ship the vulnerable version of jetty. Since the release of OCP 4.6, the metering product has been deprecated [1], hence the affected components are marked as wontfix. This may be fixed in the future. [1]…
Frequently Asked Questions
Is GHSA-j6qj-j888-vvgq in your dependencies?
O3 detects GHSA-j6qj-j888-vvgq across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.