CVE-2020-5407 | Signature Wrapping Vulnerability with spring-security-saml2-service-provider

Spring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerability during SAML response validation. When using the spring-security-saml2-service-provider component, a malicious user can carefully modify an otherwise valid SAML response and append an arbitrary assertion that Spring Security will accept as valid.

Published: 2020-05-13 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-5407 is rated Moderate Risk (59.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.66%). Review affected assets and schedule 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-2020-5407

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 2025-03-30 0.86% 0.66% -0.19%
2 2025-03-29 0.73% 0.86% +0.12%
3 2025-03-17 — 0.73% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-5407

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/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:L)
A normal user session is enough; they don’t have to be admin.
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.
 2.8 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/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:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2020-5407

GitHub Security Advisory for CVE-2020-5407

GHSA-48rw-j489-928m · Severity: high · Ecosystem: maven — Signature wrapping vulnerability in Spring Security

OS Trackers for CVE-2020-5407

vendor priority summary link
ubuntu medium CVE-2020-5407 medium priority: Ubuntu including 1 source packages (libspring-security-2.0-java), 7 status rows across 7 suites (bionic, eoan, focal, precise, trusty, upstream, xenial): DNE 5, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2020-5407

Affected software / configurations for CVE-2020-5407

Vendor Product Version Raw CPE
pivotal_software spring_security >= 5.2.0, < 5.2.4 cpe:2.3:a:pivotal_software:spring_security:*:*:*:*:*:*:*:*
pivotal_software spring_security >= 5.3.0, < 5.3.2 cpe:2.3:a:pivotal_software:spring_security:*:*:*:*:*:*:*:*

References for CVE-2020-5407

cvelogic Threat Intelligence