Advisory

GHSA-9475-xg6m-j7pw

Also known as: CVE-2020-5268

Summary

Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET

Details

Impact
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. The attacker could then use such a tocken to create a log in session.

Patches
Version 1.0.2 and 2.7.0 are patched.

Workarounds
Ensure that any IdentityProvider trusted by the Sustainsys.Saml2 SP only issues bearer tokens if the audience matches the Sustainsys.Saml2 SP.

For more information
If you have any questions or comments about this advisory:

  • Comment on #103
  • Email us at [email protected] if you think that there are further security issues.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-04-22 20:59 UTC
Modified
2026-09-10 03:48 UTC

Affected packages and fixes

Sustainsys.Saml2

NuGet · All systems

Affected

  • introduced 0, fixed 1.0.2 (ecosystem)

Fixed versions

1.0.2

Fix

The export has no generic command for this ecosystem.

Sustainsys.Saml2

NuGet · All systems

Affected

  • introduced 2.0.0, fixed 2.7.0 (ecosystem)

Fixed versions

2.7.0

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences