WSS4J validation does not use configured replay cache
Spring Web Services
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.ws:spring-ws-security Maven |
|
|
Spring Web Services
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.ws:spring-ws-security Maven |
|
|
Wss4jSecurityInterceptor did not consistently wire Apache WSS4J ReplayCache instances into RequestData for validation-time checks. As a result, protections against replay of UsernameToken nonces and creation timestamps, Timestamp elements, and certain SAML one-time-use semantics could be ineffective even when operators configured a replay cache on the interceptor.
Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.
From the CVE record · vmware
Wss4jSecurityInterceptor may fail to pass configured replay caches to Apache WSS4J during message validation. This can let an attacker replay previously valid UsernameToken, Timestamp, or certain SAML messages even when a replay cache is configured. The input does not specify authentication or user-interaction requirements.
Teams using Spring Web Services spring-ws-security versions 5.0.0–5.0.1, 4.1.0–4.1.3, 4.0.0–4.0.18, or 3.1.0–3.1.8 should check their deployments.