CVE-2021-21239
Pysaml2 Project Pysaml2 vulnerability
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.
Affected products
Pysaml2, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Pysaml2 Project Pysaml2 runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99 · Patch
- github.com/IdentityPython/pysaml2/releases/tag/v6.5.0 · Third Party Advisory
- github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62 · Third Party Advisory
- lists.debian.org/debian-lts-announce/2021/02/msg00038.html · Third Party Advisory
- pypi.org/project/pysaml2 · Third Party Advisory
- www.aleksey.com/pipermail/xmlsec/2013/009717.html · Exploit
- nvd.nist.gov/vuln/detail/CVE-2021-21239
- github.com/pypa/advisory-database/tree/main/vulns/pysaml2/PYSEC-2021-49.yaml
- nvd.nist.gov/vuln/detail/CVE-2021-21239
- cve.org/CVERecord?id=CVE-2021-21239
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.