CVE-2014-3527

Description

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.

How to fix CVE-2014-3527

To remediate CVE-2014-3527, upgrade the affected package to a fixed version below.

• —upgrade to 3.1.7 or later

Is CVE-2014-3527 being exploited?

Low — EPSS is 0.4%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 3.1.7

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2014-3527
• WEBgithub.com/spring-projects/spring-security
• WEBgithub.com/spring-projects/spring-security/commit/934937d9c1dc20c396b96c08310b72cfa627acb
• WEBgithub.com/spring-projects/spring-security/issues/2907