CVE-2014-3527: Critical severity spring security vulnerability

Published 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.

Other sources

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.

Affected Software

12 affected componentsFixes available
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
VMware Spring Security=3.1.0
VMware Spring Security=3.1.1
VMware Spring Security=3.1.2
VMware Spring Security=3.1.3
VMware Spring Security=3.1.4
VMware Spring Security=3.2.0
VMware Spring Security=3.2.1
VMware Spring Security=3.2.2
VMware Spring Security=3.2.3
VMware Spring Security=3.2.4

Event History

May 25, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
DescriptionWeakness
Sep 15, 2020
Advisory Published
via GitHub·08:16 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2014-3527?

CVE-2014-3527 has been classified as a medium-severity vulnerability.

2

How do I fix CVE-2014-3527?

To fix CVE-2014-3527, you should upgrade to Spring Security version 3.2.5 or later.

3

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.

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203