Deserialization of Untrusted Data Affecting org.amqphub.spring-amqp-10-jms-spring-boot-parent package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
1.83% (79th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-ORGAMQPHUBSPRINGAMQP10JMSSPRINGBOOTPARENT-6037949
  • published27 Oct 2023
  • disclosed19 Oct 2023

Introduced: 19 Oct 2023

CVE-2023-34050  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 org.amqphub.spring-amqp-10-jms-spring-boot-parent.

NVD Description

Note: Versions mentioned in the description apply only to the upstream org.amqphub.spring-amqp-10-jms-spring-boot-parent package and not the org.amqphub.spring-amqp-10-jms-spring-boot-parent package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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

CVSS Base Scores

version 3.1