SAML Payloads Decrypted Without Valid Signature
Spring Security
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-saml2-service-provider Maven |
|
|
Spring Security
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-saml2-service-provider Maven |
|
|
6.5.11Since Spring Security SAML decrypts SAML Responses as well as elements of SAML LogoutRequests and LogoutResponses without requiring a valid signature, attackers may be able to craft these SAML payloads and use the Service Provider as a decryption oracle.
Affected versions: Spring Security 5.7.0 through 5.7.23; 5.8.0 through 5.8.25; 6.3.0 through 6.3.16; 6.4.0 through 6.4.16; 6.5.0 through 6.5.10; 7.0.0 through 7.0.5.
From the CVE record · vmware
Spring Security's SAML service provider decrypts SAML Responses and elements of LogoutRequests and LogoutResponses without requiring a valid signature. An attacker may be able to craft these payloads and use the service provider as a decryption oracle; the input does not specify authentication or user-interaction requirements.
Teams running Spring Security's spring-security-saml2-service-provider should check versions 5.7.0–5.7.23, 5.8.0–5.8.25, 6.3.0–6.3.16, 6.4.0–6.4.16, 6.5.0–6.5.10, and 7.0.0–7.0.5.