GHSA-8vvh-crqv-jm64
HIGHGHSA-8vvh-crqv-jm64 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.qpid:qpid-broker. O3 Security confirms whether GHSA-8vvh-crqv-jm64 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Exposure of Sensitive Information to an Unauthorized Actor in Apache Qpid Broker for Java
Blast Radius
org.apache.qpid:qpid-broker☕org.apache.qpid:qpid-brokerReal-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
The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to handle user authentication. Among the choices are the SCRAM-SHA-1 and SCRAM-SHA-256 AuthenticationProvider types. It was discovered that these AuthenticationProviders in Apache Qpid Broker for Java 6.0.x before 6.0.6 and 6.1.x before 6.1.1 prematurely terminate the SCRAM SASL negotiation if the provided user name does not exist thus allowing remote attacker to determine the existence of user accounts. The Vulnerability does not apply to AuthenticationProviders other than SCRAM-SHA-1 and SCRAM-SHA-256.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.qpid:qpid-broker | ≥ 6.0.0&&< 6.0.6 | 6.0.6 |
| ☕Maven | org.apache.qpid:qpid-broker | ≥ 6.1.0&&< 6.1.1 | 6.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.qpid:qpid-broker. 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.apache.qpid:qpid-broker to 6.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8vvh-crqv-jm64 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-8vvh-crqv-jm64 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-8vvh-crqv-jm64. 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-8vvh-crqv-jm64 in your dependencies?
O3 detects GHSA-8vvh-crqv-jm64 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.