First published: Fri Apr 18 2025(Updated: )
Deserialization of Untrusted Data vulnerability in Apache ActiveMQ NMS OpenWire Client. This issue affects Apache ActiveMQ NMS OpenWire Client before 2.1.1 when performing connections to untrusted servers. Such servers could abuse the unbounded deserialization in the client to provide malicious responses that may eventually cause arbitrary code execution on the client. Version 2.1.0 introduced a allow/denylist feature to restrict deserialization, but this feature could be bypassed. The .NET team has deprecated the built-in .NET binary serialization feature starting with .NET 9 and suggests migrating away from binary serialization. The project is considering to follow suit and drop this part of the NMS API altogether. Users are recommended to upgrade to version 2.1.1, which fixes the issue. We also recommend to migrate away from relying on .NET binary serialization as a hardening method for the future.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache ActiveMQ NMS OpenWire Client | <2.1.1 | |
nuget/Apache.NMS.ActiveMQ | <2.1.1 | 2.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-29953 is classified as a critical vulnerability due to the potential for remote code execution via untrusted data deserialization.
To mitigate CVE-2025-29953, update Apache ActiveMQ NMS OpenWire Client to version 2.1.1 or later.
CVE-2025-29953 affects Apache ActiveMQ NMS OpenWire Client versions prior to 2.1.1.
Exploitation of CVE-2025-29953 can lead to unauthorized code execution and potential system compromise.
As a temporary measure, ensure connections are made only to trusted servers and limit exposure to untrusted data.