Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2014-3527

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.

Published

2017-05-25T17:29:00.257

Last Modified

2025-04-20T01:37:25.860

Status

Deferred

Source

[email protected]

Severity

CVSSv3.0: 9.8 (CRITICAL)

CVSSv2 Vector

AV:N/AC:L/Au:N/C:P/I:P/A:P

  • Access Vector: NETWORK
  • Access Complexity: LOW
  • Authentication: NONE
  • Confidentiality Impact: PARTIAL
  • Integrity Impact: PARTIAL
  • Availability Impact: PARTIAL
Exploitability Score

10.0

Impact Score

6.4

Weaknesses
  • Type: Primary
    CWE-287
Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application vmware spring_security 3.1.0 Yes
Application vmware spring_security 3.1.1 Yes
Application vmware spring_security 3.1.2 Yes
Application vmware spring_security 3.1.3 Yes
Application vmware spring_security 3.1.4 Yes
Application vmware spring_security 3.2.0 Yes
Application vmware spring_security 3.2.1 Yes
Application vmware spring_security 3.2.2 Yes
Application vmware spring_security 3.2.3 Yes
Application vmware spring_security 3.2.4 Yes
References