Authentication bypass via mismatched assertion reference
Published Jan 13, 2020 · Updated Aug 4, 2024
XML signature wrapping in IdentityPython PySAML2 before 5.0.0 allows remote attackers to substitute unverified SAML assertion data. The _check_signature method accepts a Reference URI that identifies a different assertion instead of requiring the enclosing assertion's ID. No prior application privileges or user interaction are required, but a consumer must process an attacker-supplied signed SAML document.
Summary
What happened
XML signature wrapping in IdentityPython PySAML2 before 5.0.0 allows remote attackers to substitute unverified SAML assertion data. The _check_signature method accepts a Reference URI that identifies a different assertion instead of requiring the enclosing assertion's ID. No prior application privileges or user interaction are required, but a consumer must process an attacker-supplied signed SAML document.
The record
- CVE
- CVE-2020-5390
- Published
- Jan 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Upstream XML signature-wrapping regression fixtureproof of concept · demonstrated
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