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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HApache Cxf
APPApache< 3.6.124.0.0 – 4.1.8 (excl.)4.2.0 – 4.2.3 (excl.)
Related vulnerabilities
Apache CXF: pominięcie walidacji tokenów OIDC umożliwia authentication bypass
Apache CXF: wielokrotne użycie kodu autoryzacyjnego OAuth (CWE-294)
Apache CXF: brak walidacji scope w rejestracji klienta OAuth2
Apache CXF: podmiana parametrów PKCE i OIDC przez JWT w JwtRequestCodeFilter
Apache CXF: brak walidacji pola 'aud' w tokenach JWT — Token Confusion