# CVE-2023-34050: Spring AMQP Deserialization Vulnerability

> Attackers can execute arbitrary code if untrusted users can send messages to a RabbitMQ broker using Spring AMQP without configured deserialization allowlists.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-24f5-5fmf-pwmc

## What is CVE-2023-34050?

CVE-2023-34050 is a medium-severity unsafe deserialization vulnerability in Spring AMQP, published on 19 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In spring AMQP versions 1.0.0 to
2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable class
names were added to Spring AMQP, allowing users to lock down deserialization of
data in messages from untrusted sources; however by default, when no allowed
list was provided, all classes could be deserialized.

Specifically, an application is
vulnerable if

   *  the
     SimpleMessageConverter or SerializerMessageConverter is used

   *  the user
     does not configure allowed list patterns

   *  untrusted
     message originators gain permissions to write messages to the RabbitMQ
     broker to send malicious content

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-34050?

It affects 1 product.


Products: Vmware Spring Advanced Message Queuing Protocol.

## How do I fix CVE-2023-34050?

No fix has been published for CVE-2023-34050 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-34050 being exploited?

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

Public exploit code:

- PoC of Spring AMQP Deserialization Vulnerability (CVE-2023-34050) (github_poc): https://github.com/X1r0z/spring-amqp-deserialization

## Other vulnerabilities in Spring AMQP

- [CVE-2026-59272](https://insights.sbomify.com/CVE-2026-59272/): Log4j2 AmqpAppender disables TLS hostname verification by default (medium 6.8)
- [CVE-2026-59275](https://insights.sbomify.com/CVE-2026-59275/): Deserialization in Spring AMQP (medium 6.6)
- [CVE-2026-59320](https://insights.sbomify.com/CVE-2026-59320/): In Spring AMQP the link credit never replenished on listener exception path (medium 6.5)
- [CVE-2026-47860](https://insights.sbomify.com/CVE-2026-47860/): Unbounded decompression of attacker-supplied compressed message bodies (medium 6.5)
- [CVE-2021-22095](https://insights.sbomify.com/CVE-2021-22095/): Deserialization of Untrusted Data in Spring AMQP (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34050 and fix it if it is affected.

What it is: CVE-2023-34050 is a medium-severity unsafe deserialization vulnerability in Spring AMQP, published on 19 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-34050 in the wild and no public exploit code.

Affected product: Spring AMQP. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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