GHSA-48rw-j489-928m CVE-2020-5407

Signature wrapping vulnerability in Spring Security

High Maven

Severity: 8.8 / 10; High · CVSS 3.1
Exploit chance (EPSS): 1.20%; Chance of exploitation in the next 30 days. Higher than 68.16% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-347 Improper Verification of Cryptographic Signature
Fix: 5.2.4; Upgrade org.springframework.security:spring-security-core to this version or later

Description

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.

Affected versions

Maven

Package	Vulnerable	Fixed in
org.springframework.security:spring-security-core	`>= 5.2.0, < 5.2.4`	`5.2.4`
org.springframework.security:spring-security-core	`>= 5.3.0, < 5.3.2`	`5.3.2`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.springframework.security:spring-security-core Maven → `5.2.4`

maven

<dependency><groupId>org.springframework.security</groupId><artifactId>spring-security-core</artifactId><version>5.2.4</version></dependency>

gradle

implementation("org.springframework.security:spring-security-core:5.2.4")

Severity breakdown

CVSS 3.1 8.8

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

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Weakness

CWE-347: Improper Verification of Cryptographic Signature

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2020-5407

Timeline

Jun 5, 2020 Published
Nov 8, 2023 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-vxf7-qj7q-83fh Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider	Low	Also affects org.springframework.security:spring-security-core
GHSA-x2wq-9x2f-fhj7 Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured	Medium	Also affects org.springframework.security:spring-security-core
GHSA-vqxh-445g-37fc Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide	Medium	Also affects org.springframework.security:spring-security-core
GHSA-8v5q-rhf3-jphm Spring Security annotation detection mechanism has authorization bypass	High	Also affects org.springframework.security:spring-security-core
GHSA-9pp5-9c7g-4r83 Spring Security authorization bypass for method security annotations on private methods	Critical	Also affects org.springframework.security:spring-security-core
GHSA-hh3m-g4qj-4835 Spring Security Vulnerable to Authorization Bypass via Security Annotations	Medium	Also affects org.springframework.security:spring-security-core
GHSA-q3v6-hm2v-pw99 Spring Framework has Authorization Bypass for Case Sensitive Comparisons	Medium	Also affects org.springframework.security:spring-security-core
GHSA-hmqf-wpq9-jq83 Spring Security Missing Authorization vulnerability	High	Also affects org.springframework.security:spring-security-core

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor