CVE-2018-11087

TLS validation error

MEDIUM
5.9
CVSS Score
Published: September 14, 2018 at 08:00 PM UTC
Updated: June 17, 2026 at 01:35 AM UTC
2 products affected across 2 vendorsRabbitmq Java ClientSpring Advanced Message Queuing Protocol

Using Spring AMQP by Pivotal?

Get instant alerts when new vulnerabilities affect Spring AMQP - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0.0 ≤ v < 1.7.101.x ≤ v < 1.7.102.0.0 ≤ v < 2.0.62.x ≤ v < 2.0.61.x2.x
Affected range stops below 1.7.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.0.6, so it looks safe — our inference, not a vendor statement
v < 4.8.04.8.1 ≤ v < 5.4.0
Affected range stops below 4.8.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.4.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

x_refsource_CONFIRMMitigationVendor Advisory
https://pivotal.io/security/cve-2018-11087

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-295

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card