Anders Abel

**Name of the Vulnerable Software and Affected Versions** Saml2 Authentication Services for ASP.NET versions before 1.0.2 Saml2 Authentication Services for ASP.NET versions 2.0.0 through 2.6.0 **Description** 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. The attacker could then use such a token to create a log in session. 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. **Recommendations** For versions before 1.0.2, update to version 1.0.2 to resolve the issue. For versions 2.0.0 through 2.6.0, update to version 2.7.0 to resolve the issue. As a temporary workaround, ensure that any IdentityProvider trusted by the Sustainsys.Saml2 SP only issues bearer tokens if the audience matches the Sustainsys.Saml2 SP.

**Name of the Vulnerable Software and Affected Versions** Sustainsys.Saml2 versions 2.0.0 through 2.4.x **Description** The issue concerns a faulty implementation of Token Replay Detection, an important defense measure for Single Sign On solutions. This faulty implementation affects the specified versions of the Sustainsys.Saml2 NuGet package for ASP.NET. Token Replay Detection is crucial for preventing replay attacks, where an attacker intercepts and reuses a valid token to gain unauthorized access. The correct implementation of Token Replay Detection is essential for the security of Single Sign On solutions. **Recommendations** For versions 2.0.0 through 2.4.x, update to version 2.5.0 or later, as it includes the necessary patches for the faulty Token Replay Detection implementation. At the moment, there is no information about other workarounds for the affected versions.