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 (77.9th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 78th percentile — 77.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.018 · newest: 0.018 · change: 0.000
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)
Frequently asked questions
- What is CVE-2014-3527?
- CVE-2014-3527 is a critical-severity vulnerability in Pivotal Spring Security, classified under Improper Authentication. CVSS score: 9.8/10. Published 2017-05-25.
- How severe is CVE-2014-3527?
- Critical severity. CVSS v3 base score is 9.8 out of 10.