Uncontrolled Resource Consumption in Artemis and HornetQ
Red Hat, Inc. HornetQ/Artemis
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.hornetq:hornetq-server Maven |
|
|
| org.apache.activemq:artemis-native Maven |
|
|
Red Hat, Inc. HornetQ/Artemis
| Product | Affected | Fixed in |
|---|---|---|
| org.hornetq:hornetq-server Maven |
|
|
| org.apache.activemq:artemis-native Maven |
|
|
It was found that when Artemis and HornetQ before 2.4.0 are configured with UDP discovery and JGroups discovery a huge byte array is created when receiving an unexpected multicast message. This may result in a heap memory exhaustion, full GC, or OutOfMemoryError.
From the CVE record · redhat
HornetQ and Artemis before 2.4.0 can create a huge byte array when configured with UDP discovery and JGroups discovery and receiving an unexpected multicast message. This can exhaust heap memory, trigger full garbage collection, or cause an OutOfMemoryError. The input does not specify authentication or user-interaction requirements.
Engineers running Maven org.hornetq:hornetq-server before 2.4.0.Final or org.apache.activemq:artemis-native before 2.4.0 should check their deployments.