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.
This CVE record has been updated after NVD enrichment efforts were completed. Enrichment data supplied by the NVD may require amendment due to these changes.
Description
PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. Users of pysaml2 that use the default CryptoBackendXmlSec1 backend and need to verify signed SAML documents are impacted. PySAML2 does not ensure that a signed SAML document is correctly signed. The default CryptoBackendXmlSec1 backend is using the xmlsec1 binary to verify the signature of signed SAML documents, but by default xmlsec1 accepts any type of key found within the given document. xmlsec1 needs to be configured explicitly to only use only _x509 certificates_ for the verification process of the SAML document signature. This is fixed in PySAML2 6.5.0.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
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 [email protected].
OR
*cpe:2.3:a:pysaml2_project:pysaml2:*:*:*:*:*:*:*:* versions up to (excluding) 6.5.0
Changed
Reference Type
https://github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99 No Types Assigned
https://github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99 Patch, Third Party Advisory
Changed
Reference Type
https://github.com/IdentityPython/pysaml2/releases/tag/v6.5.0 No Types Assigned
https://github.com/IdentityPython/pysaml2/releases/tag/v6.5.0 Third Party Advisory
Changed
Reference Type
https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62 No Types Assigned
https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62 Third Party Advisory
Changed
Reference Type
https://pypi.org/project/pysaml2 No Types Assigned
https://pypi.org/project/pysaml2 Product, Third Party Advisory
Changed
Reference Type
https://www.aleksey.com/pipermail/xmlsec/2013/009717.html No Types Assigned
https://www.aleksey.com/pipermail/xmlsec/2013/009717.html Exploit, Mailing List, Third Party Advisory
Added
CVSS V2 Metadata
Victim must voluntarily interact with attack mechanism
CVE Modified by GitHub, Inc.1/26/2021 1:16:17 PM
Action
Type
Old Value
New Value
Changed
Description
PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. Users of pysaml2 that use the default CryptoBackendXmlSec1 backend and need to verify signed SAML documents are impacted. PySAML2 does not ensure that a signed SAML document is correctly signed. The default CryptoBackendXmlSec1 backend is using the xmlsec1 binary to verify the signature of signed SAML documents, but by default xmlsec1 accepts any type of key found within the given document. xmlsec1 needs to be configured explicitly to only use only _x509 certificates_ for the verification process of the SAML document signature.
This is fixed in PySAML2 6.5.0.
PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. Users of pysaml2 that use the default CryptoBackendXmlSec1 backend and need to verify signed SAML documents are impacted. PySAML2 does not ensure that a signed SAML document is correctly signed. The default CryptoBackendXmlSec1 backend is using the xmlsec1 binary to verify the signature of signed SAML documents, but by default xmlsec1 accepts any type of key found within the given document. xmlsec1 needs to be configured explicitly to only use only _x509 certificates_ for the verification process of the SAML document signature. This is fixed in PySAML2 6.5.0.
Quick Info
CVE Dictionary Entry: CVE-2021-21239 NVD
Published Date: 01/21/2021 NVD
Last Modified: 11/21/2024
Source: GitHub, Inc.