You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
NIST has updated the
NVD program announcement page with additional information regarding
recent concerns and the temporary delays in enrichment efforts.
CVE-2020-5268
Detail
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 Analysts use publicly available information to associate vector strings and CVSS scores. We also display any CVSS information provided within the CVE List from the CNA.
Note: It is possible that the NVD CVSS may not match that of the CNA. The most common reason for this is that publicly available information does not provide sufficient detail or that information simply was not available at the time the CVSS vector string was assigned.
NVD Analysts use publicly available information to associate vector strings and CVSS scores. We also display any CVSS information provided within the CVE List from the CNA.
Note: NVD Analysts have published a CVSS score for this CVE based on publicly available information at the time of analysis. The CNA has not provided a score within the CVE List.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to nvd@nist.gov.
OR
*cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:* versions up to (excluding) 1.0.2
*cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:* versions from (including) 2.0.0 up to (excluding) 2.0.7
OR
*cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:* versions up to (excluding) 1.0.2
*cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:* versions from (including) 2.0.0 up to (excluding) 2.7.0
Initial Analysis by NIST4/30/2020 1:28:20 PM
Action
Type
Old Value
New Value
Added
CPE Configuration
OR
*cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:* versions up to (excluding) 1.0.2
*cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:* versions from (including) 2.0.0 up to (excluding) 2.0.7
Added
CVSS V2
NIST (AV:N/AC:M/Au:S/C:P/I:P/A:N)
Added
CVSS V2 Metadata
Victim must voluntarily interact with attack mechanism
Added
CVSS V3.1
NIST AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Added
CWE
NIST CWE-287
Changed
Reference Type
https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241 No Types Assigned
https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241 Patch, Third Party Advisory
Changed
Reference Type
https://github.com/Sustainsys/Saml2/issues/712 No Types Assigned
https://github.com/Sustainsys/Saml2/issues/712 Third Party Advisory
Changed
Reference Type
https://github.com/Sustainsys/Saml2/security/advisories/GHSA-9475-xg6m-j7pw No Types Assigned
https://github.com/Sustainsys/Saml2/security/advisories/GHSA-9475-xg6m-j7pw Mitigation, Third Party Advisory
Changed
Reference Type
https://www.nuget.org/packages/Sustainsys.Saml2/ No Types Assigned
https://www.nuget.org/packages/Sustainsys.Saml2/ Third Party Advisory
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 inc
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 inco
In Saml2 Authentication Services for ASP.NET before versions 2.7.0 and 1.0.2, 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
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 inc
Quick Info
CVE Dictionary Entry: CVE-2020-5268 NVD
Published Date: 04/21/2020 NVD
Last Modified: 05/06/2020
Source: GitHub, Inc.
) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
