When using the CAS Proxy ticket authentication from Spring Security 3.1 to 3.2.4 a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request. This means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed. If users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users.
oryginał ENCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HVMware Spring Security
APPVmware3.1.03.1.13.1.23.1.33.1.43.2.03.2.13.2.23.2.33.2.4
Powiązane podatności
VMware Spring Security — brak zapisu nagłówków HTTP odpowiedzi
Using "**" as a pattern in Spring Security configuration for WebFlux creates a mismatch in pattern matching b...
Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rule...
In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatc...
An application using spring-security-saml2-service-provider and the REDIRECT binding for SAML 2.0 Login or Log...