CyberRota Analysis
AI-GeneratedThe RabbitMQ Java client library prior to version 5.33.0 is vulnerable to a denial of service attack due to inconsistent validation of the negotiated AMQP frame_max value, allowing a malicious broker to send oversized frames. This can lead to client-side disruptions as the client may allocate and decode invalid frames instead of rejecting them. Organizations using affected Java and JVM-based applications with RabbitMQ should prioritize upgrading to version 5.33.0 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, the AMQP connection tuning path records the negotiated AMQP frame_max value, but src/main/java/com/rabbitmq/client/impl/SocketFrameHandler.java and NettyFrameHandlerFactory continue to validate broker-controlled frame payload lengths against maxInboundMessageBodySize because the negotiated limit is not applied consistently through setMaxInboundFramePayloadSize. A malicious or compromised broker can send a method frame larger than the negotiated frame_max during or after connection establishment, causing the client to allocate and decode a protocol-invalid frame instead of rejecting it with MalformedFrameException. The protocol violation can disrupt the affected connection and cause client-side denial of service. This issue is fixed in version 5.33.0.