Skip to content
Fencer Vulns
medium 5.0

CVE-2023-34050 json

Spring AMQP Deserialization Vulnerability

published 2023-10-19 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-38167

cvss
5.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

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

Patch / fix

  • Spring Spring AMQP 2.4.17, 3.0.10

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-34050 updated cvss 4.3

springframework-amqp: Deserialization Vulnerability

  • Red Hat A-MQ Clients 2 org.amqphub.spring-amqp-10-jms-spring-boot-parent org.amqphub.spring-amqp-10-jms-spring-boot-parent
    affected: workaround, no fix available
  • Red Hat build of Apache Camel for Spring Boot 3 spring-amqp
    affected: workaround, no fix planned “Will not fix”
  • Red Hat AMQ Clients
    fixed: vendor fix RHSA-2023:7697
  • Red Hat A-MQ Clients 2 org.apache.logging.log4j-log4j org.apache.logging.log4j-log4j Red Hat Enterprise Linux 9 log4j, log4j-jcl, log4j-slf4j
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

1.84% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.0 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected products

  • Spring Spring AMQP

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.