GHSA-p8qj-fj6r-w7q9
MEDIUMGHSA-p8qj-fj6r-w7q9 is a medium-severity (CVSS 4) CWE-295 vulnerability in org.springframework.amqp:spring-amqp. O3 Security confirms whether GHSA-p8qj-fj6r-w7q9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spring AMQP Core: Missing Certificate and Hostname Verification for amqps URIs in RabbitConnectionFactoryBean
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-p8qj-fj6r-w7q9.
Real-World Exposure
org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqp☕org.springframework.amqp:spring-amqpReal-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
Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(true) get TLS encryption with no certificate validation and no hostname verification.
Affected versions: Spring AMQP 4.0.0 through 4.0.3; 3.2.0 through 3.2.10; 3.1.0 through 3.1.15; 2.4.0 through 2.4.17.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.amqp:spring-amqp | ≥ 4.0.0&&< 4.0.4 | 4.0.4 |
| ☕Maven | org.springframework.amqp:spring-amqp | ≥ 3.2.0&&< 3.2.11 | 3.2.11 |
| ☕Maven | org.springframework.amqp:spring-amqp | ≥ 3.1.0 | No fix |
| ☕Maven | org.springframework.amqp:spring-amqp | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.amqp:spring-amqp. 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.springframework.amqp:spring-amqp to 4.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p8qj-fj6r-w7q9 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-p8qj-fj6r-w7q9 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-p8qj-fj6r-w7q9. 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-p8qj-fj6r-w7q9 in your dependencies?
O3 detects GHSA-p8qj-fj6r-w7q9 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.