#VU50365 Improper Verification of Cryptographic Signature in Python implementation of SAML2 - CVE-2021-21239

 

#VU50365 Improper Verification of Cryptographic Signature in Python implementation of SAML2 - CVE-2021-21239

Published: January 21, 2021 / Updated: July 19, 2024


Vulnerability identifier: #VU50365
Vulnerability risk: Medium
CVSSv4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P/U:Green
CVE-ID: CVE-2021-21239
CWE-ID: CWE-347
Exploitation vector: Remote access
Exploit availability: Public exploit is available
Vulnerable software:
Python implementation of SAML2
Software vendor:
IdentityPython

Description

The vulnerability allows a remote non-authenticated attacker to manipulate data.

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.


Remediation

Install update from vendor's website.

External links