Pivotal Spring AMQP, 1.x versions prior to 1.7.10 and 2.x versions prior to 2.0.6, expose a man-in-the-middle vulnerability due to lack of hostname validation. A malicious user that has the ability to intercept traffic would be able to view data in transit.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| pivotal_software | spring_advanced_message_queuing_protocol | 1.0.0 - 1.7.10 | - |
| pivotal_software | spring_advanced_message_queuing_protocol | 2.0.0 - 2.0.6 | - |
| vmware | rabbitmq_java_client |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4
Affected Products
2
References
pivotal_software / spring_advanced_message_queuing_protocol
| 4.8.0 |
| - |
| vmware | rabbitmq_java_client | 4.8.1 - 5.4.0 | - |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploitability
Impact