CVE-2023-46120 — Uncontrolled Resource Consumption

Vendor	Product	Version range	Fixed in
rabbitmq	rabbitmq-java-client	< 5.18.0	5.18.0
vmware	rabbitmq_java_client	< 5.18.0	5.18.0

GHSA

RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max

ghsa·2026-08-18·CVSS 7.5

CVE-2026-61634 [HIGH] CWE-20 RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max ## Summary The max body size was enforced to patch CVE-2023-46120, but even though that limit still works, the frame size itself still exceeds the given max size. ## Root cause The Java client records the AMQP 0-9-1 `frame_max` negotiated during connection tuning, but the socket inbound frame reader continues to validate broker-controlled payload lengths against the much larger `maxInboundMessageBodySize` limit. A broker peer can therefore send a method frame whose payload is larger than the negotiated `frame_max`, have it allocated and decoded, and complete the connection handshake instead of being rejected as a protocol violation. *Reported by Team Atlanta.*

OSV

CVE-2023-46120: The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes

osv·2023-10-25·CVSS 7.5

CVE-2023-46120 [HIGH] CVE-2023-46120: The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. `maxBodyLebgth` was not used when receiving Message objects. Attackers could send a very large Message causing a memory overflow and triggering an OOM Error. Users of RabbitMQ may suffer from DoS attacks from RabbitMQ Java client which will ultimately exhaust the memory of the consumer. This vulnerability was patched in version 5.18.0.

OSV

RabbitMQ Java client's Lack of Message Size Limitation leads to Remote DoS Attack

osv·2023-10-24

CVE-2023-46120 [MEDIUM] RabbitMQ Java client's Lack of Message Size Limitation leads to Remote DoS Attack RabbitMQ Java client's Lack of Message Size Limitation leads to Remote DoS Attack ### Summary `maxBodyLebgth` was not used when receiving Message objects. Attackers could just send a very large Message causing a memory overflow and triggering an OOM Error. ### PoC #### RbbitMQ * Use RabbitMQ 3.11.16 as MQ and specify Message Body size 512M (here it only needs to be larger than the Consumer memory) * Start RabbitMQ #### Producer * Build a String of length 256M and send it to Consumer ``` package org.springframework.amqp.helloworld; import org.springframework.amqp.core.AmqpTemplate; import org.springframework.context.ApplicationContext; import org.springframework.context.annotation.AnnotationConfigApplicationContext; public class Producer { public static void main(String[] args) { Appli

GHSA

RabbitMQ Java client's Lack of Message Size Limitation leads to Remote DoS Attack

ghsa·2023-10-24

CVE-2023-46120 [MEDIUM] CWE-400 RabbitMQ Java client's Lack of Message Size Limitation leads to Remote DoS Attack RabbitMQ Java client's Lack of Message Size Limitation leads to Remote DoS Attack ### Summary `maxBodyLebgth` was not used when receiving Message objects. Attackers could just send a very large Message causing a memory overflow and triggering an OOM Error. ### PoC #### RbbitMQ * Use RabbitMQ 3.11.16 as MQ and specify Message Body size 512M (here it only needs to be larger than the Consumer memory) * Start RabbitMQ #### Producer * Build a String of length 256M and send it to Consumer ``` package org.springframework.amqp.helloworld; import org.springframework.amqp.core.AmqpTemplate; import org.springframework.context.ApplicationContext; import org.springframework.context.annotation.AnnotationConfigApplicationContext; public class Producer { public static void main(String[] args) { Appli

CISA ICS

Siemens SINEC NMS

cisa_ics·2024-08-15·CVSS 7.0

[HIGH] Siemens SINEC NMS ICS Advisory ## Siemens SINEC NMS Release DateAugust 15, 2024 Alert CodeICSA-24-228-06 Related topics: Industrial Control System Vulnerabilities, Industrial Control Systems As of January 10, 2023, CISA will no longer be updating ICS security advisories for Siemens product vulnerabilities beyond the initial advisory. For the most up-to-date information on vulnerabilities in this advisory, please see Siemens' ProductCERT Security Advisories (CERT Services | Services | Siemens Global). View CSAF ## 1. EXECUTIVE SUMMARY - CVSS v4 9.4 - ATTENTION: Exploitable remotely/low attack complexity - Vendor: Siemens - Equipment: SINEC NMS - Vulnerabilities: Use After Free, Improper Input Validation, Deserialization of Untrusted Data, Improper Restriction of Operations

CISA ICS

Siemens SINEC NMS

cisa_ics·2024-02-15

Siemens SINEC NMS ICS Advisory ## Siemens SINEC NMS Release DateFebruary 15, 2024 Alert CodeICSA-24-046-15 As of January 10, 2023, CISA will no longer be updating ICS security advisories for Siemens product vulnerabilities beyond the initial advisory. For the most up-to-date information on vulnerabilities in this advisory, please see Siemens' ProductCERT Security Advisories (CERT Services | Services | Siemens Global). View CSAF ## 1. EXECUTIVE SUMMARY - CVSS v3 9.8 - ATTENTION: Exploitable remotely/low attack complexity - Vendor: Siemens - Equipment: SINEC NMS - Vulnerabilities: Out-of-bounds Read, Inadequate Encryption Strength, Double Free, Use After Free, NULL Pointer Dereference, Improper Input Validation, Missing Encryption of Sensitive Data, Allocation of Resources Wit

CVE-2023-46120: The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. `maxBodyLebgth` was not used when…

Affected

CVSS provenance