GitHub Advisoryadvisory · PyPI

GHSA-5p3x-r448-pc62 Improper Verification of Cryptographic Signature in PySAML2

MEDIUM Published 2021-01-21 Modified 2024-10-14 Official page ↗
Aliases
CVE-2021-21239
Ecosystem
PyPI
Packages
pysaml2
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Weaknesses
CWE-347
Reviewed
2021-01-21

Affected packages

• PyPI pysaml2: < 6.5.0 → fixed in 6.5.0

Description

Impact All users of pysaml2 that use the default `CryptoBackendXmlSec1` backend and need to verify signed SAML documents are impacted. `pysaml2 <= 6.4.1` 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. Patches Users should upgrade to pysaml2 `v6.5.0`. Workarounds No workaround provided at this point. References This issue has been reported in the past at the xmlsec1 mailing list: https://www.aleksey.com/pipermail/xmlsec/2013/009717.html Credits • Brian Wolff For more information If you have any questions or comments about this advisory: • Open an issue in pysaml2 • Email us at the incident-response address

Related

Alias · CVE (1)

  • CVE-2021-21239 PySAML2 is a pure python implementation of SAML Version 2 Standard. vulnerability

Weakness · CWE (1)

  • CWE-347 Improper Verification of Cryptographic Signature weakness

References