WSS4J validation does not use configured replay cache
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.1.9, 4.0.19, 4.1.3.1 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring | >=3.1.0 <3.1.9, >=4.0.0 <4.0.19, >=4.1.0 <4.1.3.1, >=5.0.0 <5.0.1.1 | 3.1.9, 4.0.19, 4.1.3.1, 5.0.1.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket