You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
CVE-2023-46120 - High Severity Vulnerability
Vulnerable Library - amqp-client-5.1.2.jar
The RabbitMQ Java client library allows Java applications to interface with RabbitMQ.
Library home page: http://www.rabbitmq.com
Path to dependency file: /pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/com/rabbitmq/amqp-client/5.1.2/amqp-client-5.1.2.jar
Dependency Hierarchy:
Found in HEAD commit: 34ce0f6524391068ef5b880f65575eb3eb499124
Found in base branch: master
Vulnerability Details
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.Publish Date: 2023-10-25
URL: CVE-2023-46120
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-mm8h-8587-p46h
Release Date: 2023-10-25
Fix Resolution (com.rabbitmq:amqp-client): 5.18.0
Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-amqp): 3.2.0
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: