Missing Token Replay Detection in Saml2 Authentication services for ASP.NET
Published 25 Mar 2020 · Updated 8 Jul 2026
Is your project on an affected Sustainsys.Saml2?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=2.0.0 <2.5.0
- Fixed in
- 2.5.0
dotnet add package Sustainsys.Saml2 --version 2.5.0Details
Impact
Token Replay Detection is an important defence in depth measure for Single Sign On solutions. In all previous 2.X versions, the Token Replay Detection is not properly implemented.
Note that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use.
Patches
The 2.5.0 version is patched.
Workarounds
There are no workarounds with existing versions. Fixing the issue requires code updates.
References
https://en.wikipedia.org/wiki/Replay_attack
For more information
If you have any questions or comments about this advisory:
- Comment on #711.
- Email us at [security@sustainsys.com](mailto:security@susatinsys.com) if you think that there are further security issues.
Is GHSA-g6j2-ch25-5mmv in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Sustainsys.Saml2, and gives you the command that fixes it.
More advisories for Sustainsys.Saml2
- HighCVE-2023-41890Sustainsys.Saml2 Insufficient Identity Provider Issuer Validation · 20 Sept 2023
- MediumCVE-2020-5268Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET · 22 Apr 2020
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.