Unencoded HTML Outputs in Spring Security May Allow Cross-Site Scripting
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.11An attacker able to influence values in RelyingPartyRegistration may be able to run arbitrary code on HTML forms generated by Spring Security filters.
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 filters generate HTML forms using values from RelyingPartyRegistration. An attacker who can influence those values may be able to run arbitrary code in the generated forms. The input does not specify authentication or user-interaction requirements.
Teams using the Maven package org.springframework.security:spring-security-saml2-service-provider should check Spring Security 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.