CVE-2020-5261: Missing Token Replay Detection
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. Saml2 Authentication services for ASP.NET (NuGet package Sustainsys.Saml2) greater than 2.0.0, and less than version 2.5.0 have a faulty implementation of Token Replay Detection. Token Replay Detection is an important defense measure for Single Sign On solutions. The 2.5.0 version is patched. Note that version 1.0.1 and prior versions are not affected. These versions have a correct Token Replay Implementation and are safe to use.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
NuGet package Sustainsys.Saml2 (Saml2 Authentication services for ASP.NET)to a version that resolves this vulnerability.Fixed in 2.5.0
Event History
Frequently Asked Questions
What is the severity of CVE-2020-5261?
CVE-2020-5261 has a medium severity rating due to its impact on Token Replay Detection in authentication services.
How do I fix CVE-2020-5261?
To fix CVE-2020-5261, upgrade the Sustainsys.Saml2 NuGet package to version 2.5.0 or later.
What software is affected by CVE-2020-5261?
CVE-2020-5261 affects Sustainsys.Saml2 versions greater than 2.0.0 and less than 2.5.0.
Why is Token Replay Detection important in CVE-2020-5261?
Token Replay Detection is crucial for preventing unauthorized access in Single Sign-On solutions.
What is the impact of CVE-2020-5261 on security?
CVE-2020-5261 compromises the security of authentication mechanisms that rely on Token Replay Detection, increasing the risk of replay attacks.