Vulnerabilities · 2014 · Vmware
CVE-2014-3527
Vmware Spring Security vulnerability
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Spring Security. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Vmware Spring Security runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- pivotal.io/security/cve-2014-3527 · Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2014-3527
- github.com/spring-projects/spring-security/issues/2907
- github.com/spring-projects/spring-security/commit/934937d9c1dc20c396b96c08310b72cfa627acb
- github.com/advisories/GHSA-wmv4-5w76-vp9g
- nvd.nist.gov/vuln/detail/CVE-2014-3527
- cve.org/CVERecord?id=CVE-2014-3527
More vulnerabilities in Vmware products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.