CVE-2021-21238: SAML XML Signature wrapping

Published Jan 21, 2021
·
Updated

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 validate the SAML document against an XML schema. This allows invalid XML documents to trick the verification process, by presenting elements with a valid signature inside elements whose content has been malformed. The verification is offloaded to xmlsec1 and xmlsec1 will not validate every signature in the given document, but only the first it finds in the given scope.

Patches

Users should upgrade to pysaml2 v6.5.0.

Workarounds

No workaround provided at this point.

References

No references provided at this point.

Credits

- Victor Schönfelder Garcia (isits AG International School of IT Security) - Juraj Somorovsky (Paderborn University) - Vladislav Mladenov (Ruhr University Bochum)

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

Other sources

PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0.

Affected Software

2 affected componentsFixes available
pip/pysaml2<6.5.0
6.5.0
Pysaml2 Project Pysaml2<6.5.0

Event History

Jan 21, 2021
Advisory Published
via GitHub·02:12 PM
CVE Published
via MITRE·02:15 PM
Data Sourced
via MITRE·02:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2021-21238?

CVE-2021-21238 is considered to have a moderate severity level due to the potential for invalid SAML documents to bypass verification processes.

2

How do I fix CVE-2021-21238?

To fix CVE-2021-21238, upgrade to pysaml2 version 6.5.0 or later.

3

What does CVE-2021-21238 affect?

CVE-2021-21238 affects all users of pysaml2 who utilize the default CryptoBackendXmlSec1 backend for verifying signed SAML documents.

4

What is the main issue described in CVE-2021-21238?

The main issue in CVE-2021-21238 is the lack of validation against an XML schema for SAML documents in pysaml2 versions up to 6.4.1.

5

Can I still use pysaml2 if I'm affected by CVE-2021-21238?

While you can still use pysaml2 if affected by CVE-2021-21238, it is essential to upgrade to the secure version to avoid potential security risks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203