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…

Description

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.

Scores

EPSS (exploitation in 30 days)

1.8% · top 21% of all CVEs (4 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Weakness

• Access Control Bypass
• CWE-287 (opens in a new tab)All about CWE-287 and its CVEs

Affected products

• Pivotal · Spring Security

  • affected 3.1 to 3.2.4

Affected packages

From reviewed advisories of the GitHub Advisory Database.

• Mavenorg.springframework.security:spring-security-coreGHSA-wmv4-5w76-vp9g (opens in a new tab)

References (1)

• https://pivotal.io/security/cve-2014-3527 (opens in a new tab)x_refsource_CONFIRMx_transferred

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisory GHSA-wmv4-5w76-vp9g (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2014-3527](https://trackcve.app/badge/CVE-2014-3527.svg)](https://trackcve.app/cve/CVE-2014-3527)

Record last updated 6 Aug 2024, 10:50 UTC.