Description
WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header, leading to incorrect confidentiality coverage and possible policy bypass.
Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Apache Software Foundation | Apache WSS4J | 4.0.0 – < 4.0.2, 3.0.0 – < 3.0.6, < 2.4.4 | 4.0.2 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | wss4j | No fix yet | — |
| Debian 13 | wss4j | No fix yet | — |
| Debian 12 | wss4j | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | wss4j | No fix yet | — |
| Ubuntu 26.04 LTS | wss4j | No fix yet | — |
| Ubuntu 24.04 LTS | wss4j | No fix yet | — |
| Ubuntu 22.04 LTS | wss4j | No fix yet | — |
| Ubuntu 20.04 LTS | wss4j | No fix yet | — |
Show 2 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 18.04 LTS | wss4j | No fix yet | — |
| Ubuntu 16.04 LTS | wss4j | No fix yet | — |