SOAP security faults leak Spring Security account state
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 |
|
|
Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with generic authentication errors. That behavior assists remote attackers in distinguishing valid accounts from invalid ones and inferring lifecycle state.
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
Spring Web Services integration paths with Spring Security can expose detailed account state through exception messages or callback outcomes instead of generic authentication errors. Remote SOAP clients may use these responses to distinguish valid from invalid accounts and infer whether an account is locked or disabled.
Teams running Spring Web Services with 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.