CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0CVE-2023-41890 – Sustainsys.Saml2 Insufficient Identity Provider Issuer Validation
https://notcve.org/view.php?id=CVE-2023-41890
Sustainsys.Saml2 library adds SAML2P support to ASP.NET web sites, allowing the web site to act as a SAML2 Service Provider. Prior to versions 1.0.3 and 2.9.2, when a response is processed, the issuer of the Identity Provider is not sufficiently validated. This could allow a malicious identity provider to craft a Saml2 response that is processed as if issued by another identity provider. It is also possible for a malicious end user to cause stored state intended for one identity provider to be used when processing the response from another provider. An application is impacted if they rely on any of these features in their authentication/authorization logic: the issuer of the generated identity and claims; or items in the stored request state (AuthenticationProperties). This issue is patched in versions 2.9.2 and 1.0.3. • https://github.com/Sustainsys/Saml2/issues/712 https://github.com/Sustainsys/Saml2/issues/713 https://github.com/Sustainsys/Saml2/security/advisories/GHSA-fv2h-753j-9g39 • CWE-289: Authentication Bypass by Alternate Name CWE-294: Authentication Bypass by Capture-replay •
CVSS: 7.3EPSS: 0%CPEs: 2EXPL: 0CVE-2020-5268 – Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET
https://notcve.org/view.php?id=CVE-2020-5268
In Saml2 Authentication Services for ASP.NET versions before 1.0.2, and between 2.0.0 and 2.6.0, there is a vulnerability in how tokens are validated in some cases. Saml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved. The Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. • https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241 https://github.com/Sustainsys/Saml2/issues/712 https://github.com/Sustainsys/Saml2/security/advisories/GHSA-9475-xg6m-j7pw https://www.nuget.org/packages/Sustainsys.Saml2 • CWE-287: Improper Authentication CWE-303: Incorrect Implementation of Authentication Algorithm •
CVSS: 8.2EPSS: 0%CPEs: 1EXPL: 0CVE-2020-5261 – Missing Token Replay Detection
https://notcve.org/view.php?id=CVE-2020-5261
Saml2 Authentication services for ASP.NET (NuGet package Sustainsys.Saml2) greater than 2.0.0, and less than version 2.5.0 has a faulty implementation of Token Replay Detection. Token Replay Detection is an important defence in depth measure for Single Sign On solutions. The 2.5.0 version is patched. Note that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use. • https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241 https://github.com/Sustainsys/Saml2/issues/711 https://github.com/Sustainsys/Saml2/security/advisories/GHSA-g6j2-ch25-5mmv • CWE-294: Authentication Bypass by Capture-replay •