GHSA-q35w-85pq-rv3x
HIGHGHSA-q35w-85pq-rv3x is a high-severity (CVSS 7.5) CWE-552 vulnerability in fish.payara.distributions:payara. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-q35w-85pq-rv3x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Payara, when deployed to the root context, allows attackers to visit META-INF and WEB-INF
Blast Radius
fish.payara.distributions:payara☕fish.payara.distributions:payara☕fish.payara.distributions:payaraReal-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
Payara before 2022-11-04, when deployed to the root context, allows attackers to visit META-INF and WEB-INF, a different vulnerability than CVE-2022-37422. This affects Payara Platform Community before 4.1.2.191.38, 5.x before 5.2022.4, and 6.x before 6.2022.1, and Payara Platform Enterprise before 5.45.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | fish.payara.distributions:payara | ≥ 6.2021.1.Alpha1&&< 6.2022.2 | 6.2022.2 |
| ☕Maven | fish.payara.distributions:payara | ≥ 5.0.0.Alpha1&&< 5.2022.5 | 5.2022.5 |
| ☕Maven | fish.payara.distributions:payara | all versions | No fix |
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 fish.payara.distributions:payara. 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 fish.payara.distributions:payara to 6.2022.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q35w-85pq-rv3x 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-q35w-85pq-rv3x 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-q35w-85pq-rv3x. 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-q35w-85pq-rv3x in your dependencies?
O3 detects GHSA-q35w-85pq-rv3x across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.