Maven package
org.springframework.amqp/spring-amqp
pkg:maven/org.springframework.amqp/spring-amqp
Vulnerabilities (5)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-22095 | — | >= 2.2.0, < 2.2.20 | 2.2.20 | Nov 30, 2021 | In Spring AMQP versions 2.2.0 - 2.2.19 and 2.3.0 - 2.3.11, the Spring AMQP Message object, in its toString() method, will create a new String object from the message body, regardless of its size. This can cause an OOM Error with a large message | ||
| CVE-2021-22097 | — | >= 2.2.0, < 2.2.19 | 2.2.19 | Oct 28, 2021 | In Spring AMQP versions 2.2.0 - 2.2.18 and 2.3.0 - 2.3.10, the Spring AMQP Message object, in its toString() method, will deserialize a body for a message with content type application/x-java-serialized-object. It is possible to construct a malicious java.util.Dictionary object t | ||
| CVE-2018-11087 | Med | 5.9 | >= 2.0.0, < 2.0.6 | 2.0.6 | Sep 14, 2018 | Pivotal Spring AMQP, 1.x versions prior to 1.7.10 and 2.x versions prior to 2.0.6, expose a man-in-the-middle vulnerability due to lack of hostname validation. A malicious user that has the ability to intercept traffic would be able to view data in transit. | |
| CVE-2017-8045 | Cri | 9.8 | < 1.5.7 | 1.5.7 | Nov 27, 2017 | In Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, an org.springframework.amqp.core.Message may be unsafely deserialized when being converted into a string. A malicious payload could be crafted to exploit this and enable a remote code execution attack. | |
| CVE-2016-2173 | Cri | 9.8 | < 1.5.5 | 1.5.5 | Apr 21, 2017 | org.springframework.core.serializer.DefaultDeserializer in Spring AMQP before 1.5.5 allows remote attackers to execute arbitrary code. |
- CVE-2021-22095Nov 30, 2021affected >= 2.2.0, < 2.2.20fixed 2.2.20
In Spring AMQP versions 2.2.0 - 2.2.19 and 2.3.0 - 2.3.11, the Spring AMQP Message object, in its toString() method, will create a new String object from the message body, regardless of its size. This can cause an OOM Error with a large message
- CVE-2021-22097Oct 28, 2021affected >= 2.2.0, < 2.2.19fixed 2.2.19
In Spring AMQP versions 2.2.0 - 2.2.18 and 2.3.0 - 2.3.10, the Spring AMQP Message object, in its toString() method, will deserialize a body for a message with content type application/x-java-serialized-object. It is possible to construct a malicious java.util.Dictionary object t
- affected >= 2.0.0, < 2.0.6fixed 2.0.6
Pivotal Spring AMQP, 1.x versions prior to 1.7.10 and 2.x versions prior to 2.0.6, expose a man-in-the-middle vulnerability due to lack of hostname validation. A malicious user that has the ability to intercept traffic would be able to view data in transit.
- affected < 1.5.7fixed 1.5.7
In Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, an org.springframework.amqp.core.Message may be unsafely deserialized when being converted into a string. A malicious payload could be crafted to exploit this and enable a remote code execution attack.
- affected < 1.5.5fixed 1.5.5
org.springframework.core.serializer.DefaultDeserializer in Spring AMQP before 1.5.5 allows remote attackers to execute arbitrary code.