Advisory

GHSA-5p3x-r448-pc62

Also known as: CVE-2021-21239, PYSEC-2021-49

Summary

Improper Verification of Cryptographic Signature in PySAML2

Details

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:

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2021-01-21 14:12 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

pysaml2

PyPI · All systems

Affected

  • introduced 0, fixed 6.5.0 (ecosystem)

Fixed versions

6.5.0

Fix

  • Fixed version 6.5.0
    pip install --upgrade pysaml2==6.5.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences