CVE-2020-5268
Summary
| CVE | CVE-2020-5268 |
|---|
| State | PUBLIC |
|---|
| Assigner | [email protected] |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2020-04-21 17:15:00 UTC |
|---|
| Updated | 2020-05-06 17:26:00 UTC |
|---|
| Description | In Saml2 Authentication Services for ASP.NET versions before 1.0.2, and between 2.0.0 and 2.6.0, there is a vulnerability in how tokens are validated in some cases. 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 token to create a log in session. This vulnerability is patched in versions 1.0.2 and 2.7.0. |
|---|
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|
| Fix token replay detection · Sustainsys/Saml2@e58e0a1 · GitHub |
MISC |
github.com |
Patch, Third Party Advisory |
| Subject Confirmation Method not Validated · Advisory · Sustainsys/Saml2 · GitHub |
CONFIRM |
github.com |
Mitigation, Third Party Advisory |
| NuGet Gallery
| Sustainsys.Saml2 2.7.0 |
MISC |
www.nuget.org |
Third Party Advisory |
| Reserved Issue# · Issue #712 · Sustainsys/Saml2 · GitHub |
MISC |
github.com |
Third Party Advisory |
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
Legacy QID Mappings
- 983865 Dotnet (nuget) Security Update for Sustainsys.Saml2 (GHSA-9475-xg6m-j7pw)
