CVE-2023-46604

Отчет

If the openwire protocol IS NOT in use, system operators can disable the OpenWire protocol which removes most risk of this vulnerability being exploited. If OpenWire IS being used, see the Mitigations section for potential options to reduce your attack surface.

• How to determine if an AMQ 7 system is affected: Check in the broker.xml configuration file. Notice the presence of OPENWIRE in the following snippet which indicates a vulnerable configuration.

• How to determine if an AMQ 7 for OpenShift system is affected: Get the ActivemqArtemis CR yaml and review the acceptor protocol and see if the following entry is present: (default, all, Openwire) which indicates the system is vulnerable.
• How to determine if a Fuse 6 system is affected: By default Fuse 6 includes and enables ActiveMQ Broker. So unless this has been manually disabled, every Fuse 6 system is affected by this vulnerability.
• How to determine if a Fuse 7 system is affected: Fuse 7 itself is not vulnerable. By default it ships the vulnerable activemq-client jar, however it does not instantiate an ActiveMQ broker. If this feature (connect to an external ActiveMQ Broker) were manually configured, it would make it vulnerable.
• How to determine if a Fuse Online system is affected: Syndesis, an Integration Platform As A Service part of Fuse Online which runs on top of Openshift, does not use activemq code. Also, it doesn't instantiate a broker with Openwire protocol enabled, which makes it not vulnerable to this CVE.

Меры по смягчению последствий

In affected systems, it may be possible to mitigate some of the risks from this vulnerability. However this mitigation cannot eliminate all risks; the only complete resolution is to apply software updates. On systems where the broker is exposed to the public network, use firewall rules to restrict the transport ports and enable SSL to protect this "Transport".