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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-1357 | 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. |
Github GHSA |
GHSA-wmv4-5w76-vp9g | Authorization Bypass in Spring Security |
References
History
No history.
Status: PUBLISHED
Assigner: dell
Published:
Updated: 2024-08-06T10:50:16.372Z
Reserved: 2014-05-14T00:00:00.000Z
Link: CVE-2014-3527
No data.
Status : Deferred
Published: 2017-05-25T17:29:00.257
Modified: 2025-04-20T01:37:25.860
Link: CVE-2014-3527
OpenCVE Enrichment
No data.
EUVD
Github GHSA