WSS4J validation does not use configured replay cache
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.0.1.1, 4.1.3.1, 4.0.19, 3.1.9, 5.0.2, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Spring Spring Web Services
From 5.0.0 · fixed in 5.0.1.1; From 4.1.0 · fixed in 4.1.3.1; From 4.0.0 · fixed in 4.0.19; From 3.1.0 · fixed in 3.1.9
- org.springframework.ws:spring-ws-securityMaven
From 5.0.0 · fixed in 5.0.2
- org.springframework.ws:spring-ws-securityMaven
From 4.1.0 · fixed in 4.1.4
- org.springframework.ws:spring-ws-securityMaven
From 4.0.0 · through 4.0.18
- org.springframework.ws:spring-ws-securityMaven
From 3.1.0 · through 3.1.8