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. 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.

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.

### 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.

### 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.

Los servicios de autenticación Saml2 para ASP.NET (paquete NuGet Sustainsys.Saml2) superior a la versión 2.0.0 y menor que la versión 2.5.0 tienen una implementación defectuosa de la detección de reproducción de tokens. Token Replay Detection es una defensa importante en la medida de profundidad para las soluciones de Single Sign On. La versión 2.5.0 está parcheada. Tenga en cuenta que la versión 1.0.1 no se ve afectada. Tiene una implementación correcta de reproducción de tokens y es seguro de usar. Los servicios de autenticación Saml2 para ASP.NET (paquete NuGet Sustainsys.Saml2) superior a la versión 2.0.0 y menor que la versión 2.5.0 tienen una implementación defectuosa de la detección de reproducción de tokens. La detección de reproducción de tokens es una medida de defensa importante para las soluciones de inicio de sesión único. La versión 2.5.0 está parcheada. Tenga en cuenta que la versión 1.0.1 y las versiones anteriores no se ven afectadas. Estas versiones tienen una implementación correcta de reproducción de tokens y son seguras de usar.