Source: python-pysaml2 Version: 6.1.0-3 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team <t...@security.debian.org>
Hi, The following vulnerability was published for python-pysaml2. CVE-2021-21239[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. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-21239 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21239 [1] https://github.com/IdentityPython/pysaml2/commit/751dbf50a51131b13d55989395f9b115045f9737 [2] https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
