# CVE-2018-11087: TLS validation error

> Attackers can intercept and view data in transit due to missing hostname validation in TLS connections.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w4g2-9hj6-5472

## What is CVE-2018-11087?

CVE-2018-11087 is a medium-severity vulnerability in Pivotal Spring AMQP, published on 14 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2018-11087?

8 open source packages ship an affected version, including org.springframework.amqp:spring-amqp and com.rabbitmq:amqp-client. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.amqp:spring-amqp` | Maven | All versions | 1.7.10 |
| `org.springframework.amqp:spring-amqp` | Maven | All versions | 1.7.10 |
| `org.springframework.amqp:spring-amqp` | Maven | From 2.0.0 | 2.0.6 |
| `org.springframework.amqp:spring-amqp` | Maven | From 2.0.0 | 2.0.6 |
| `com.rabbitmq:amqp-client` | Maven | All versions | 4.8.0 |
| `com.rabbitmq:amqp-client` | Maven | All versions | 4.8.0 |
| `com.rabbitmq:amqp-client` | Maven | From 5.0.0 | 5.4.0 |
| `com.rabbitmq:amqp-client` | Maven | From 5.0.0 | 5.4.0 |

Products: Pivotal Software Spring Advanced Message Queuing Protocol, Vmware Rabbitmq Java Client.

## How do I fix CVE-2018-11087?

Upgrade org.springframework.amqp:spring-amqp to a fixed version for your release line: 1.7.10 or 2.0.6.

## Is CVE-2018-11087 being exploited?

There is no known exploitation of CVE-2018-11087 in the wild and no public exploit code.

## Other vulnerabilities in Pivotal Spring AMQP

- [CVE-2017-8045](https://insights.sbomify.com/CVE-2017-8045/): Deserialization of Untrusted Data in Spring AMQP (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11087 and fix it if it is affected.

What it is: CVE-2018-11087 is a medium-severity vulnerability in Pivotal Spring AMQP, published on 14 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11087 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.amqp:spring-amqp (Maven): affected all versions; fixed in 1.7.10
- org.springframework.amqp:spring-amqp (Maven): affected all versions; fixed in 1.7.10
- org.springframework.amqp:spring-amqp (Maven): affected from 2.0.0; fixed in 2.0.6
- org.springframework.amqp:spring-amqp (Maven): affected from 2.0.0; fixed in 2.0.6
- com.rabbitmq:amqp-client (Maven): affected all versions; fixed in 4.8.0
- com.rabbitmq:amqp-client (Maven): affected all versions; fixed in 4.8.0
- com.rabbitmq:amqp-client (Maven): affected from 5.0.0; fixed in 5.4.0
- com.rabbitmq:amqp-client (Maven): affected from 5.0.0; fixed in 5.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-11087/ (Markdown: https://insights.sbomify.com/CVE-2018-11087/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-11087
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-11087
- OSV: https://osv.dev/vulnerability/CVE-2018-11087

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-11087/
Summaries are generated and may contain mistakes; the official description above is the record.