Auth bypass in Pivotal Spring Security
CVE-2014-3527
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.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.018, 79.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Pivotal Spring Security — versions 3.1 to 3.2.4
- VMware Spring Security — versions 3.1.0, 3.1.1, 3.1.2
Weakness classification (CWE)
References
- pivotal.io/security/cve-2014-3527 (Vendor Advisory)