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
Weakness
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Spring_advanced_message_queuing_protocol | Vmware | 2.2.0 (including) | 2.2.19 (excluding) |
| Spring_advanced_message_queuing_protocol | Vmware | 2.3.0 (including) | 2.3.11 (excluding) |
| Spring | Ubuntu | bionic | * |
| Spring | Ubuntu | focal | * |
| Spring | Ubuntu | hirsute | * |
| Spring | Ubuntu | impish | * |
| Spring | Ubuntu | kinetic | * |
| Spring | Ubuntu | lunar | * |
| Spring | Ubuntu | mantic | * |
| Spring | Ubuntu | oracular | * |
| Spring | Ubuntu | plucky | * |
| Spring | Ubuntu | trusty | * |
| Spring | Ubuntu | xenial | * |
Potential Mitigations
- Make fields transient to protect them from deserialization.
- An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.