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.
References
Link Resource
https://pivotal.io/security/cve-2014-3527 Vendor Advisory
History

No history.

cve-icon MITRE Information

Status: PUBLISHED

Assigner: dell

Published: 2017-05-25T17:00:00

Updated: 2017-05-25T16:57:01

Reserved: 2014-05-14T00:00:00


Link: CVE-2014-3527

JSON object: View

cve-icon NVD Information

Status : Analyzed

Published: 2017-05-25T17:29:00.257

Modified: 2021-06-08T18:22:35.140


Link: CVE-2014-3527

JSON object: View

cve-icon Redhat Information

No data.

CWE