Cyber Resilience

CVE-2023-34050

MediumRCE

Published: 19 October 2023

Published
19 October 2023
Modified
21 November 2024
KEV Added
Patch
CVSS Score v3.1 5.0 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H
EPSS Score 0.4304 97.6th percentile
Risk Priority 36 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2023-34050 is a medium-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Vmware Spring Advanced Message Queuing Protocol. Its CVSS base score is 5.0 (Medium).

Operationally, ranked in the top 2.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis

In Spring AMQP versions 1.0.0 to 2.4.16 and 3.0.0 to 3.0.9, the addition of allowed-list patterns for deserializable class names left a default configuration in which all classes could be deserialized when no list was supplied. The issue affects applications that use the SimpleMessageConverter or SerializerMessageConverter without configuring allowed-list patterns, exposing them to deserialization of untrusted data (CWE-502) with a CVSS 3.1 score of 5.0.

An attacker who obtains write access to a RabbitMQ broker can send a message containing a malicious serialized payload. When the vulnerable converter processes the message, the payload is deserialized, enabling the attacker to influence object instantiation and achieve limited integrity impact together with high availability impact on the receiving application.

The Spring security advisory at https://spring.io/security/cve-2023-34050 recommends configuring allowed-list patterns to restrict deserializable classes and upgrading to a patched release. The associated EPSS score has remained at 0.4304 with no material increase since disclosure.

EU & UK References

Vulnerability details

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,…

more

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

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

vmware
spring advanced message queuing protocol
1.0.0 — 2.4.16 · 3.0.0 — 3.0.9

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-502

Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.

addresses: CWE-502

Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.

addresses: CWE-502

Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.

addresses: CWE-502

Validates or rejects untrusted serialized data before deserialization occurs.

addresses: CWE-502

Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.

addresses: CWE-502

Integrity verification of serialized information can detect tampering before deserialization occurs.

addresses: CWE-502

Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.

References