Description
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.
Remediation
References
https://pivotal.io/security/cve-2014-3527
Related Vulnerabilities
CVE-2013-1965 Vulnerability in maven package org.apache.struts:struts2-showcase
CVE-2023-26136 Vulnerability in npm package tough-cookie
CVE-2020-1958 Vulnerability in maven package org.apache.druid.extensions:druid-basic-security
CVE-2016-4986 Vulnerability in maven package org.tap4j:tap
CVE-2020-13925 Vulnerability in maven package org.apache.kylin:kylin-server