SOAP security faults leak Spring Security account state
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.
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.
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