~ / search / GHSA-c825-6ph3-4h84

GHSA-c825-6ph3-4h84

Apache ActiveMQ is Vulnerable to Integer Overflow or Wraparound

Source: GitHub Advisory Database (reviewed) Moderate CVE-2025-66168

Packages

EcosystemPackageAffectedFixed in
Maven org.apache.activemq:apache-activemq < 5.19.2 5.19.2
Maven org.apache.activemq:apache-activemq >= 6.0.0, < 6.1.9 6.1.9
Maven org.apache.activemq:apache-activemq >= 6.2.0, < 6.2.1 6.2.1
Maven org.apache.activemq:activemq-all < 5.19.2 5.19.2
Maven org.apache.activemq:activemq-all >= 6.0.0, < 6.1.9 6.1.9
Maven org.apache.activemq:activemq-all >= 6.2.0, < 6.2.1 6.2.1
Maven org.apache.activemq:activemq-mqtt < 5.19.2 5.19.2
Maven org.apache.activemq:activemq-mqtt >= 6.0.0, < 6.1.9 6.1.9
Maven org.apache.activemq:activemq-mqtt >= 6.2.0, < 6.2.1 6.2.1

Details

As written in the advisory (Markdown source, shown as plain text).

Apache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted. This issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0 Users are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.

References

External links from the advisory. They lead to third-party sites.