GHSA-pj33-75x5-32j4
MEDIUMRabbitMQ HTTP API's queue deletion endpoint does not verify that the user has a required permission
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.
Blast Radius
rabbit_commonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Queue deletion via the HTTP API was not verifying the configure permission of the user.
Impact
Users who had all of the following:
- Valid credentials
- Some permissions for the target virtual host
- HTTP API access
could delete queues it had no (deletion) permissions for.
Workarounds
Disable management plugin and use, for example, Prometheus and Grafana for monitoring.
OWASP Classification
OWASP Top10 A01:2021 – Broken Access Control
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💧Hex | rabbit_common | ≥ 3.12.7&&< 3.12.11 | 3.12.11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rabbit_common. 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 rabbit_common to 3.12.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pj33-75x5-32j4 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-pj33-75x5-32j4 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-pj33-75x5-32j4. 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-pj33-75x5-32j4 in your dependencies?
O3 detects GHSA-pj33-75x5-32j4 across Hex dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.