CVE-2021-21239: Improper Verification of Cryptographic Signature in PySAML2
(updated )
All users of pysaml2 that use the default CryptoBackendXmlSec1
backend and need to verify signed SAML documents are impacted. pysaml2 <= 6.4.1
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.
References
- github.com/IdentityPython/pysaml2
- github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99
- github.com/IdentityPython/pysaml2/releases/tag/v6.5.0
- github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62
- github.com/advisories/GHSA-5p3x-r448-pc62
- github.com/pypa/advisory-database/tree/main/vulns/pysaml2/PYSEC-2021-49.yaml
- lists.debian.org/debian-lts-announce/2021/02/msg00038.html
- nvd.nist.gov/vuln/detail/CVE-2021-21239
- pypi.org/project/pysaml2
- www.aleksey.com/pipermail/xmlsec/2013/009717.html
Detect and mitigate CVE-2021-21239 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →