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-25 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2014-3527 is rated High Risk (67.1/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.81%). Core evidence: EPSS rose +1.45% over the last day, indicating growing attacker interest. Mandatory action: High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2014-3527

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.36% 1.81% +1.45%
2 2025-03-30 0.64% 0.36% -0.28%
3 2025-03-29 0.64%

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2014-3527

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
10.0 6.4 [email protected]

Weakness enumeration for CVE-2014-3527

GitHub Security Advisory for CVE-2014-3527

GHSA-wmv4-5w76-vp9g · Severity: critical · Ecosystem: maven — Authorization Bypass in Spring Security

OS Trackers for CVE-2014-3527

vendor priority summary link
redhat high https://access.redhat.com/security/cve/CVE-2014-3527
ubuntu medium CVE-2014-3527 medium priority: Ubuntu including 1 source packages (libspring-security-2.0-java), 12 status rows across 12 suites (artful, bionic, cosmic, disco, precise, trusty, upstream, vivid, wily, xenial, yakkety, zesty): DNE 8, ignored 3, needs-triage 1. https://ubuntu.com/security/CVE-2014-3527

Affected software / configurations for CVE-2014-3527

Vendor Product Version Raw CPE
vmware spring_security 3.1.0 cpe:2.3:a:vmware:spring_security:3.1.0:*:*:*:*:*:*:*
vmware spring_security 3.1.1 cpe:2.3:a:vmware:spring_security:3.1.1:*:*:*:*:*:*:*
vmware spring_security 3.1.2 cpe:2.3:a:vmware:spring_security:3.1.2:*:*:*:*:*:*:*
vmware spring_security 3.1.3 cpe:2.3:a:vmware:spring_security:3.1.3:*:*:*:*:*:*:*
vmware spring_security 3.1.4 cpe:2.3:a:vmware:spring_security:3.1.4:*:*:*:*:*:*:*
vmware spring_security 3.2.0 cpe:2.3:a:vmware:spring_security:3.2.0:*:*:*:*:*:*:*
vmware spring_security 3.2.1 cpe:2.3:a:vmware:spring_security:3.2.1:*:*:*:*:*:*:*
vmware spring_security 3.2.2 cpe:2.3:a:vmware:spring_security:3.2.2:*:*:*:*:*:*:*
vmware spring_security 3.2.3 cpe:2.3:a:vmware:spring_security:3.2.3:*:*:*:*:*:*:*
vmware spring_security 3.2.4 cpe:2.3:a:vmware:spring_security:3.2.4:*:*:*:*:*:*:*

References for CVE-2014-3527

cvelogic Threat Intelligence