Authentication bypass via appended arbitrary SAML assertion
Published May 13, 2020 · Updated Sep 16, 2024
Signature wrapping in Spring Security 5.2.0 through 5.2.3 and 5.3.0 through 5.3.1 allows remote authenticated users to impersonate SAML users. The SAML response validator verifies an otherwise valid response but then accepts an appended arbitrary assertion as the authenticated identity. Exploitation requires access to a valid SAML response and an application configured with the spring-security-saml2-service-provider component, enabling impersonation within that application.
Summary
What happened
Signature wrapping in Spring Security 5.2.0 through 5.2.3 and 5.3.0 through 5.3.1 allows remote authenticated users to impersonate SAML users. The SAML response validator verifies an otherwise valid response but then accepts an appended arbitrary assertion as the authenticated identity. Exploitation requires access to a valid SAML response and an application configured with the spring-security-saml2-service-provider component, enabling impersonation within that application.
The record
- CVE
- CVE-2020-5407
- Published
- May 13, 2020
- Updated
- Sep 16, 2024
- Vendor
- Spring
- Product
- Spring Security
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2 <5.2.4
- Affected versionversion=5.3 <5.3.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo