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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: dell
Published: 2017-05-25T17:00:00
Updated: 2024-08-06T10:50:16.372Z
Reserved: 2014-05-14T00:00:00
Link: CVE-2014-3527
Vulnrichment
No data.
NVD
Status : Modified
Published: 2017-05-25T17:29:00.257
Modified: 2024-11-21T02:08:18.343
Link: CVE-2014-3527
Redhat