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 |
https://pivotal.io/security/cve-2014-3527 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 02:08
Type | Values Removed | Values Added |
---|---|---|
References | () https://pivotal.io/security/cve-2014-3527 - Vendor Advisory |
Information
Published : 2017-05-25 17:29
Updated : 2024-11-21 02:08
NVD link : CVE-2014-3527
Mitre link : CVE-2014-3527
CVE.ORG link : CVE-2014-3527
JSON object : View
Products Affected
vmware
- spring_security
CWE
CWE-287
Improper Authentication