Authentication bypass via mismatched SAML issuers
Published Sep 19, 2023 · Updated Oct 15, 2024
Authentication bypass in Sustainsys.Saml2 before 1.0.3 and 2.0.0 through 2.9.1 allows remote attackers to forge identity claims. Response processing validates the response issuer through signing keys but fails to verify that the assertion issuer matches it or the issuer bound to stored request state. Exploitation requires an application to trust the generated issuer or AuthenticationProperties, enabling substitution of another provider's identity or state.
Summary
What happened
Authentication bypass in Sustainsys.Saml2 before 1.0.3 and 2.0.0 through 2.9.1 allows remote attackers to forge identity claims. Response processing validates the response issuer through signing keys but fails to verify that the assertion issuer matches it or the issuer bound to stored request state. Exploitation requires an application to trust the generated issuer or AuthenticationProperties, enabling substitution of another provider's identity or state.
The record
- CVE
- CVE-2023-41890
- Published
- Sep 19, 2023
- Updated
- Oct 15, 2024
- Vendor
- Sustainsys
- Product
- Sustainsys.Saml2
- Classifications
- CWE-294, CWE-289, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2023CVE publishedPublication date reported by the CVE source.
- Oct 15, 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=< 1.0.3
- Affected versionversion=>= 2.0.0, < 2.9.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