Spring AMQP Vulnerability: Untrusted Deserialization of Data
CVE-2023-34050

5MEDIUM

Key Information:

Vendor

Spring

Status
Spring AMQp
Vendor
CVE Published:
19 October 2023

Badges

👾 Exploit Exists🟡 Public PoC🟣 EPSS 43%

What is CVE-2023-34050?

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

Affected Version(s)

Spring AMQP MacOS 1.0.0 < 2.4.17

Spring AMQP MacOS 3.0.0 < 3.0.10

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

spring-amqp-deserialization
Created by X1r0z

References

https://spring.io/security/cve-2023-34050

EPSS Score

43% chance of being exploited in the next 30 days.

CVSS V3.1

Score:
5
Severity:
MEDIUM
Confidentiality:
None
Integrity:
Low
Availability:
None
Attack Vector:
Network
Attack Complexity:
High
Privileges Required:
High
User Interaction:
None
Scope:
Unchanged

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

.