Spring Advanced Message Queuing Protocol
Approved changes feed: RSS · Atom
cpe:2.3:a:vmware:spring_advanced_message_queuing_protocol:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Vmware (7bb62c7c-2241-5a0b-8dbc-5f13251fb24e) |
|---|---|
| Product | Spring Advanced Message Queuing Protocol (ab7509b0-75a5-5207-9cf2-2bd1cefa6877) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/spring-projects/spring-amqp |
purl2cpe | 2026-06-01 10:12:21.680011 |
pkg:maven/org.springframework.amqp/spring-amqp |
purl2cpe | 2026-06-01 10:12:21.680012 |
pkg:nuget/Spring.Messaging.Amqp |
purl2cpe | 2026-06-01 10:12:21.680014 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-34050 |
vulnerable | 2026-06-08 06:06:24.319098 |
Spring AMQP Deserialization Vulnerability
MEDIUM (5)
In spring AMQP versions 1.0.0 to
2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable class
names were added to Spring AMQP, allowing users to lock down deserialization of
data in messages from untrusted sources; however by default, when no allowed
list was provided, all classes could be deserialized.
Specifically, an application is
vulnerable if
* the
SimpleMessageConverter or SerializerMessageConverter is used
* the user
does not configure allowed list patterns
* untrusted
message originators gain permissions to write messages to the RabbitMQ
broker to send malicious content
Published: 2023-10-19T07:11:35.038Z
Updated: 2024-09-12T17:58:46.718Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-22097 |
vulnerable | 2026-06-08 05:29:59.794551 |
Details available
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 that can cause 100% CPU usage in the application if the toString() method is called.
Published: 2021-10-28T15:24:19.000Z
Updated: 2024-08-03T18:30:24.007Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-22095 |
vulnerable | 2026-06-08 05:29:59.787665 |
Details available
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
Published: 2021-11-30T18:41:35.000Z
Updated: 2024-08-03T18:30:23.925Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-2173 |
vulnerable | 2026-06-08 05:07:33.494563 |
Details available
org.springframework.core.serializer.DefaultDeserializer in Spring AMQP before 1.5.5 allows remote attackers to execute arbitrary code.
Published: 2017-04-21T20:00:00.000Z
Updated: 2024-08-05T23:17:50.583Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.