Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET
cve-program · CVE-2020-5268
PublishedIn 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.
Read the publisher's advisoryeuvd · EUVD-2020-0374
PublishedIn 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.
Read the publisher's advisorynvd · CVE-2020-5268
PublishedIn 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.
Read the publisher's advisoryosv · GHSA-9475-xg6m-j7pw
Published### Impact 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 tocken to create a log in session. ### Patches Version 1.0.2 and 2.7.0 are patched. ### Workarounds Ensure that any IdentityProvider trusted by the Sustainsys.Saml2 SP only issues bearer tokens if the audience matches the Sustainsys.Saml2 SP. ### For more information If you have any questions or comments about this advisory: * Comment on #103 * Email us at [email protected] if you think that there are further security issues.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2020-5268 · CVE overview and exploitation status
cve-program · CVE-2020-5268
- https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241
- https://github.com/Sustainsys/Saml2/security/advisories/GHSA-9475-xg6m-j7pw
- https://github.com/Sustainsys/Saml2/issues/712
- https://www.nuget.org/packages/Sustainsys.Saml2/
euvd · EUVD-2020-0374
- https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241
- https://github.com/Sustainsys/Saml2/security/advisories/GHSA-9475-xg6m-j7pw
- https://github.com/Sustainsys/Saml2/issues/712
- https://www.nuget.org/packages/Sustainsys.Saml2/
nvd · CVE-2020-5268
- https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241
- https://github.com/Sustainsys/Saml2/issues/712
- https://github.com/Sustainsys/Saml2/security/advisories/GHSA-9475-xg6m-j7pw
- https://www.nuget.org/packages/Sustainsys.Saml2/
osv · GHSA-9475-xg6m-j7pw
Related changes
Linked by CVE identifierNo related changes are available here.