PT-2021-14350

CVE-2021-21239

·

Published

2021-01-21

·

Updated

2026-10-31

Description by

CVSS 4.0
6.9
Medium
MetricsAV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Name of the Vulnerable Software and Affected Versions: PySAML2 versions prior to 6.5.0
Description: The issue is related to an improper verification of cryptographic signatures in PySAML2, a pure python implementation of SAML Version 2 Standard. Users of PySAML2 that use the default CryptoBackendXmlSec1 backend and need to verify signed SAML documents are impacted. The default CryptoBackendXmlSec1 backend uses 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 x509 certificates for the verification process of the SAML document signature.
Recommendations: For PySAML2 versions prior to 6.5.0, upgrade to PySAML2 version 6.5.0 to resolve the issue. As a temporary workaround, consider configuring xmlsec1 to only use x509 certificates for the verification process of the SAML document signature. Restrict access to the default CryptoBackendXmlSec1 backend to minimize the risk of exploitation. Avoid using the default CryptoBackendXmlSec1 backend until the issue is resolved.
Exploitability
Exploit
Fix
Impacts
Researchers
Vendors
Affected products
Related identifiers
GHSA-5P3X-R448-PC62
ALT-PU-2023-1286
ALT-PU-2023-1534
CLEANSTART-2025-MA81386
DLA-2577-1
OPENSUSE-SU-2024:11258-1
OPENSUSE-SU-2024:14156-1
OPENSUSE-SU-2026:11524-1
PYSEC-2021-49
SUSE-SU-2021:1962-1
SUSE-SU-2021:2554-1
USN-5066-1
USN-5066-2
Found an issue in the description? Have something to add? Feel free to write us 👾