Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.6.12, 4.1.8 and 4.2.3.
Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place. Any attacker able to place a message on the service's JMS destination can submit a malicious serialized object, leading to denial of service or, if a suitable gadget class is on the classpath, remote code execution. The fix disables ObjectMessage deserialization by default, with a configuration switch to re-enable it if needed. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Apache Software Foundation | <3.6.12, >=4.0.0 <4.1.8, >=4.2.0 <4.2.3 | 3.6.12, 4.1.8, 4.2.3 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket