Apache.NMS.ActiveMQ
Apache NMS (.Net Standard Messaging Library): Openwire implementation of Apache NMS API
Activity
- Latest release
- 9mo ago
- Total releases
- 16
- Cadence
- ~8 months
- Last 12 months
- 1
Details
- First release
- Feb 04, 2011
| Version | Released | |
|---|---|---|
2.2.0
minor
|
2.2.0
minor
Dependencies (2)
|
|
2.1.1
patch
|
2.1.1
patch
Dependencies (3)
|
|
2.1.0
minor
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
2.1.0
minor
Dependencies (3)
|
|
2.0.1
patch
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
2.0.1
patch
Dependencies (3)
|
|
2.0.0
major
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
2.0.0
major
Dependencies (3)
|
|
1.8.0
minor
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.8.0
minor
Dependencies (2)
|
|
1.7.2
patch
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.7.2
patch
Dependencies (1)
|
|
1.7.1
patch
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.7.1
patch
Dependencies (1)
|
|
1.7.0
minor
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.7.0
minor
Dependencies (1)
|
|
1.6.3
patch
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.6.3
patch
Dependencies (1)
|
|
1.6.2
patch
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.6.2
patch
Dependencies (1)
|
|
1.6.0
minor
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.6.0
minor
Dependencies (1)
|
|
1.5.6
patch
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.5.6
patch
Dependencies (1)
|
|
1.5.4
patch
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.5.4
patch
Dependencies (1)
|
|
1.5.1
minor
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.5.1
minor
Dependencies (1)
|
|
1.4.1
initial
1 CVE
CVE-2025-29953
GHSA-9g64-r942-fvmp
Apr 18, 2025
Apache ActiveMQ NMS OpenWire Client Deserialization of Untrusted Data vulnerability
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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. Affected versions
1.4.1
1.5.1
1.5.4
1.5.6
1.6.0
1.6.2
1.6.3
1.7.0
1.7.1
1.7.2
1.8.0
2.0.0
+ 2 more Show less
2.0.1
2.1.0
Fixed in
2.1.1
References
Updated Apr 23, 2025 · Source: OSV.dev |
1.4.1
initial
Dependencies (1)
|