# CVE-2017-8045: Deserialization of Untrusted Data in Spring AMQP

> Attackers can achieve remote code execution by sending a malicious payload that triggers unsafe deserialization in Spring AMQP.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vqqg-xgv7-cf68

## What is CVE-2017-8045?

CVE-2017-8045 is a critical unsafe deserialization vulnerability in Spring AMQP Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, published on 27 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, an org.springframework.amqp.core.Message may be unsafely deserialized when being converted into a string. A malicious payload could be crafted to exploit this and enable a remote code execution attack.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2017-8045?

6 open source packages ship an affected version, including org.springframework.amqp:spring-amqp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.amqp:spring-amqp` | Maven | All versions | 1.5.7 |
| `org.springframework.amqp:spring-amqp` | Maven | All versions | 1.5.7 |
| `org.springframework.amqp:spring-amqp` | Maven | From 1.6.0 | 1.6.11 |
| `org.springframework.amqp:spring-amqp` | Maven | From 1.6.0 | 1.6.11 |
| `org.springframework.amqp:spring-amqp` | Maven | From 1.7.0 | 1.7.4 |
| `org.springframework.amqp:spring-amqp` | Maven | From 1.7.0 | 1.7.4 |

Products: Pivotal Software Spring Advanced Message Queuing Protocol.

## How do I fix CVE-2017-8045?

Upgrade org.springframework.amqp:spring-amqp to a fixed version for your release line: 1.5.7, 1.6.11 or 1.7.4.

## Is CVE-2017-8045 being exploited?

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

## Other vulnerabilities in Spring AMQP Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7

- [CVE-2018-11087](https://insights.sbomify.com/CVE-2018-11087/): TLS validation error (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8045 and fix it if it is affected.

What it is: CVE-2017-8045 is a critical unsafe deserialization vulnerability in Spring AMQP Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, published on 27 Nov 2017. 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-2017-8045 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.5.7
- org.springframework.amqp:spring-amqp (Maven): affected all versions; fixed in 1.5.7
- org.springframework.amqp:spring-amqp (Maven): affected from 1.6.0; fixed in 1.6.11
- org.springframework.amqp:spring-amqp (Maven): affected from 1.6.0; fixed in 1.6.11
- org.springframework.amqp:spring-amqp (Maven): affected from 1.7.0; fixed in 1.7.4
- org.springframework.amqp:spring-amqp (Maven): affected from 1.7.0; fixed in 1.7.4

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-2017-8045/ (Markdown: https://insights.sbomify.com/CVE-2017-8045/index.md)
```

## Sources

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

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