Technical impact
Apache WSS4J implements WS‑Security for Java applications and protects against replay attacks by recording identifiers such as the nonce, timestamp, signature, and SAML OneTimeUse assertion of each signed message. In vulnerable releases, the library performed a two‑step process: it first checked whether an identifier had already been seen and only after that verification did it record the identifier. If several identical copies of a message were processed concurrently, each copy could pass the check before any were recorded, allowing all copies to be accepted. Consequently, an attacker who captured a valid authenticated request while it was in transit could send multiple copies simultaneously, causing the same operation to be executed repeatedly or with altered content. The weakness is identified as a CWE‑367 Concurrent Race Condition.
Affected Systems
The problem influences all Apache WSS4J versions that employ the replay cache, specifically releases older than 4.0.3, 3.0.7, and 2.4.5. Deployments that use Apache CXF are especially affected because CXF has the replay cache enabled by default. Applications that incorporate a custom ReplayCache implementation that does not override the updated addIfAbsent method with an atomic operation are also vulnerable.
Risk and Exploitability
No EPSS score is available and the issue is not listed in the CISA KEV catalog, indicating that public exploitation has not yet been observed. The attack requires interception of a legitimate WS‑Security message and the ability to transmit several copies at once, a scenario achievable by an adversary with network visibility between client and server. The lack of an atomic check‑and‑record mechanism makes the exploit deterministic once the timing condition is met. The vulnerability can result in repeated authenticated actions and potential data corruption, but severity assessment must rely on organization‑specific risk factors and the presence or absence of mitigation.