An improper verification of cryptographic signature. 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. Upstream Advisory: https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62
Created python-pysaml2 tracking bugs for this issue: Affects: epel-8 [bug 2007589] Affects: fedora-all [bug 2007588] Affects: openstack-rdo [bug 2007590]
Upstream fix: https://github.com/IdentityPython/pysaml2/commit/751dbf50a51131b13d55989395f9b115045f9737
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2021-21239