GHSA-8qq9-r6cc-qjv9
Spring Web Services: WSS4J validation does not use configured replay cache
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | org.springframework.ws:spring-ws-security | >= 5.0.0, < 5.0.2 | 5.0.2 |
| Maven | org.springframework.ws:spring-ws-security | >= 4.1.0, < 4.1.4 | 4.1.4 |
| Maven | org.springframework.ws:spring-ws-security | >= 4.0.0, <= 4.0.18 | no fix listed |
| Maven | org.springframework.ws:spring-ws-security | >= 3.1.0, <= 3.1.8 | no fix listed |
Details
As written in the advisory (Markdown source, shown as plain text).
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.
References
External links from the advisory. They lead to third-party sites.