Severity: moderate 

Affected versions:

- Apache WSS4J 4.0.0 before 4.0.3
- Apache WSS4J 3.0.0 before 3.0.7
- Apache WSS4J before 2.4.5

Description:

Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of 
a signed message, and the ID of a SAML 2.0 "OneTimeUse" assertion, so that a 
captured message cannot be accepted twice. It checked whether a value had 
already been seen, validated the message, and only then remembered the value, 
as two separate steps. If several copies of the same message were processed at 
the same time, they could all pass the check before any of them was remembered, 
and all be accepted. An attacker who obtained a valid message before the 
recipient first processed it could send several copies at once, so that the 
same authenticated request was executed more than once. Where a UsernameToken 
is not bound to the message by a signature, the copies could carry different 
message bodies. The attacker needs to obtain the message while it is still in 
transit; a message captured after it has been accepted cannot be replayed. 
Affects deployments with a replay cache configured, as Apache CXF has by 
default. The value is now checked and remembered in a single atomic step. 
Custom ReplayCache implementations should override the new 
ReplayCache.addIfAbsent method with an operation that is atomic in their 
underlying store. Users are recommended to upgrade to versions 4.0.3 or 3.0.7 
or 2.4.5, which fix this issue.

Credit:

This issue was reported independently by Wanxin Yin (MegaVector / yaklang.io) 
and hataehoon (GitHub: @dpfkdlemtp). (finder)

References:

https://ws.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-115690

Reply via email to