com.rabbitmq:amqp-client vulnerabilities
The RabbitMQ Java client library allows Java applications to interface with RabbitMQ.
- Registry
- Maven
- Latest
- 5.38.0
- License
- AL 2.0
12 known advisories
The latest version, 5.38.0, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=com.rabbitmq:amqp-client -DdepVersion=5.38.0 -DforceVersion=trueIs your project on an affected com.rabbitmq:amqp-client?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for com.rabbitmq:amqp-client
RabbitMQ: JSONReader in the default JSON-RPC mapper never terminates on truncated input, causing DoS
- Affected
- <5.36.1
- Fixed in
- 5.36.1
RabbitMQ: Malformed UTF-8 in shortstr properties permanently disables RPC consumers
- Affected
- <5.36.0
- Fixed in
- 5.36.0
RabbitMQ Java client: plaintext broker credentials leaked in exception message from ConnectionFactoryConfigurator.load()
- Affected
- <5.35.0
- Fixed in
- 5.35.0
RabbitMQ Java client has frame-level OOM: Math.min(maxInboundMessageBodySize, 0) defeats frame size enforcement
- Affected
- <5.34.0
- Fixed in
- 5.34.0
RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max
- Affected
- <5.33.0
- Fixed in
- 5.33.0
RabbitMQ Java client: TrustEverythingTrustManager used by default in useSslProtocol() enables MITM
- Affected
- <5.33.0
- Fixed in
- 5.33.0
RabbitMQ Java client malformed body frame triggers raw command assembler exception
- Affected
- <5.31.0
- Fixed in
- 5.31.0
RabbitMQ Java client: Unvalidated Class.forName in JSON-RPC ProcedureDescription enables arbitrary class loading
- Affected
- <5.33.0
- Fixed in
- 5.33.0
RabbitMQ Java client ValueReader: Oversized LongString/bytes length triggers OOM via unchecked allocation
- Affected
- <5.33.1
- Fixed in
- 5.33.1
RabbitMQ Java client ValueReader: Unbounded recursive table/array nesting causes StackOverflowError DoS
- Affected
- <5.33.1
- Fixed in
- 5.33.1
RabbitMQ Java client's Lack of Message Size Limitation leads to Remote DoS Attack
- Affected
- <5.18.0
- Fixed in
- 5.18.0
Moderate severity vulnerability that affects com.rabbitmq:amqp-client and org.springframework.amqp:spring-amqp
- Affected
- <4.8.0 · >=5.0.0 <5.4.0
- Fixed in
- 4.8.0, 5.4.0
Is your com.rabbitmq:amqp-client version vulnerable?
- com.rabbitmq:amqp-client 5.38No known advisories in 5.38.0
- com.rabbitmq:amqp-client 5.37No known advisories in 5.37.1
- com.rabbitmq:amqp-client 5.361 advisory in 5.36.0
- com.rabbitmq:amqp-client 5.352 advisories in 5.35.0
- com.rabbitmq:amqp-client 5.343 advisories in 5.34.0
- com.rabbitmq:amqp-client 5.334 advisories in 5.33.1
- com.rabbitmq:amqp-client 4.1211 advisories in 4.12.0
- com.rabbitmq:amqp-client 4.1111 advisories in 4.11.3
- com.rabbitmq:amqp-client 4.1011 advisories in 4.10.0
- com.rabbitmq:amqp-client 4.911 advisories in 4.9.3
- com.rabbitmq:amqp-client 4.811 advisories in 4.8.3
- com.rabbitmq:amqp-client 4.712 advisories in 4.7.0
- com.rabbitmq:amqp-client 3.612 advisories in 3.6.6
- com.rabbitmq:amqp-client 3.512 advisories in 3.5.7
- com.rabbitmq:amqp-client 3.412 advisories in 3.4.4
- com.rabbitmq:amqp-client 3.312 advisories in 3.3.5
- com.rabbitmq:amqp-client 3.212 advisories in 3.2.4
- com.rabbitmq:amqp-client 3.112 advisories in 3.1.4
Which of your client projects still run an old com.rabbitmq:amqp-client?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.