Skip to content
Fencer Intel
high 8.8

CVE-2020-5407 json

Signature Wrapping Vulnerability with spring-security-saml2-service-provider

published 6y ago modified 4mo ago also GHSA-48rw-j489-928m , EUVD-2020-0457

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.security:spring-security-core 5.2.4, 5.3.2
  • Spring by VMware Spring Security 5.2.4, 5.3.2

Is CVE-2020-5407 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.security:spring-security-core
>=5.2.0, <5.2.4
>=5.3.0, <5.3.2
5.2.4
5.3.2

Affected products

  • Spring by VMware Spring Security

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.