CVE-2014-3527
First published: Thu May 25 2017(Updated: )
When using Spring Security's CAS Proxy ticket authentication 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. ## Mitigation Users of affected versions should apply the following mitigation: - Users of 3.2x should upgrade to 3.2.5 or later - Users of 3.1.x should upgrade to 3.1.7 or later ## Credit This issue was identified by David Ohsie and brought to our attention by the CAS Development team.
Credit: security_alert@emc.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| maven/org.springframework.security:spring-security-core | >=3.2.0<3.2.5 | 3.2.5 |
| maven/org.springframework.security:spring-security-core | <3.1.7 | 3.1.7 |
| Spring Security | =3.1.0 | |
| Spring Security | =3.1.1 | |
| Spring Security | =3.1.2 | |
| Spring Security | =3.1.3 | |
| Spring Security | =3.1.4 | |
| Spring Security | =3.2.0 | |
| Spring Security | =3.2.1 | |
| Spring Security | =3.2.2 | |
| Spring Security | =3.2.3 | |
| Spring Security | =3.2.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://pivotal.io/security/cve-2014-3527
- https://nvd.nist.gov/vuln/detail/CVE-2014-3527
- https://github.com/spring-projects/spring-security/issues/2907
- https://github.com/spring-projects/spring-security/commit/934937d9c1dc20c396b96c08310b72cfa627acb
- https://github.com/advisories/GHSA-wmv4-5w76-vp9g (Advisory)
Frequently Asked Questions
What is the severity of CVE-2014-3527?
CVE-2014-3527 has been classified as a medium-severity vulnerability.
How do I fix CVE-2014-3527?
To fix CVE-2014-3527, you should upgrade to Spring Security version 3.2.5 or later.
Which versions of Spring Security are affected by CVE-2014-3527?
CVE-2014-3527 affects Spring Security versions from 3.1.0 up to 3.2.4.
What is the nature of CVE-2014-3527 vulnerability?
CVE-2014-3527 involves a security issue with Proxy ticket authentication in Spring Security's CAS integration.
Is CVE-2014-3527 related to CAS Proxy ticket authentication?
Yes, CVE-2014-3527 specifically affects the CAS Proxy ticket authentication mechanism of Spring Security.
- agent/type
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-wmv4-5w76-vp9g
- alias/CVE-2014-3527
- agent/software-canonical-lookup
- agent/severity
- agent/references
- agent/weakness
- agent/description
- collector/github-advisory
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/author
- package-manager/maven
- vendor/vmware
- canonical/spring security
- version/spring security/3.1.0
- version/spring security/3.1.1
- version/spring security/3.1.2
- version/spring security/3.1.3
- version/spring security/3.1.4
- version/spring security/3.2.0
- version/spring security/3.2.1
- version/spring security/3.2.2
- version/spring security/3.2.3
- version/spring security/3.2.4