First published: Tue Jul 02 2024(Updated: )
AMQ Broker is a high-performance messaging implementation based on ActiveMQ Artemis. It uses an asynchronous journal for fast message persistence, and supports multiple languages, protocols, and platforms.<br>This release of Red Hat AMQ Broker 7.12.1 includes security and bug fixes, and enhancements. For further information, refer to the release notes linked to in the References section.<br>Security Fix(es):<br><li> (CVE-2023-5072) JSON-java: parser confusion leads to OOM</li> <li> (CVE-2024-30172) Infinite loop in ED25519 verification in the ScalarUtil class</li> <li> (CVE-2024-29857) org.bouncycastle: Importing an EC certificate with crafted F2m parameters may lead to Denial of Service</li> <li> (CVE-2024-30171) bc-java: BouncyCastle vulnerable to a timing variant of Bleichenbacher (Marvin Attack)</li> <li> (CVE-2024-34447) org.bouncycastle: Use of Incorrectly-Resolved Name or Reference</li> For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat AMQ |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2024:4271 is classified as moderate.
To fix RHSA-2024:4271, you should update to the latest version of Red Hat AMQ Broker.
RHSA-2024:4271 addresses multiple security vulnerabilities that affect Red Hat AMQ Broker.
RHSA-2024:4271 affects Red Hat AMQ Broker versions prior to 7.12.1.
There are no official workarounds provided for RHSA-2024:4271; updating is recommended.