CVE-2014-3527

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.

Risk Information

Base Score

9.8

MODERATE

Vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Score

Exploitation Probability

0.359

Associated Vulnerability

Vulnerability	OS Platform
Vulnerabilities CVE-2014-3527 are fixed in Spring-security-core 3.1.7	Windows
Vulnerabilities CVE-2014-3527 are fixed in Spring-security-core 3.2.5	Windows
Vulnerabilities CVE-2014-3527 are fixed in Spring-security-core for Linux 3.1.7	Linux
Vulnerabilities CVE-2014-3527 are fixed in Spring-security-core for Linux 3.2.5	Linux

Patch Details

No records found

References

https://nvd.nist.gov/vuln/detail/CVE-2023-1234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1234