X.509 authentication bypasses Spring Security account checks
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 |
|
|
X509AuthenticationProvider could issue a fully authenticated X509AuthenticationToken when a presented certificate mapped to UserDetails, without applying Spring Security's standard account lifecycle checks (disabled, locked, expired, or credentials-expired accounts).
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
X509AuthenticationProvider can issue a fully authenticated X509AuthenticationToken when a presented certificate maps to UserDetails, without checking whether the account is disabled, locked, expired, or has expired credentials. This can allow authentication for an account that should be rejected. The input does not specify network or local access requirements or user interaction.
Teams running Spring Web Services 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 spring-ws-security dependency.