CVE-2020-5390: High severity Pysaml2 Project Pysaml2 vulnerability

Published Jan 13, 2020
·
Updated

Last updated 25 August 2025

Other sources

PySAML2 before 5.0.0 does not check that the signature in a SAML document is enveloped and thus signature wrapping is effective, i.e., it is affected by XML Signature Wrapping (XSW). The signature information and the node/object that is signed can be in different places and thus the signature verification will succeed, but the wrong data will be used. This specifically affects the verification of assertion that have been signed.

Launchpad

PySAML2 before 5.0.0 does not check that the signature in a SAML document is enveloped and thus signature wrapping is effective, i.e., it is affected by XML Signature Wrapping (XSW). The signature information and the node/object that is signed can be in different places and thus the signature verification will succeed, but the wrong data will be used. This specifically affects the verification of assertions that have been signed.

GitHub

Affected Software

10 affected componentsFixes available
pip/pysaml2<5.0.0
5.0.0
Pysaml2 Project Pysaml2<5.0.0
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.04
Canonical Ubuntu Linux=19.10
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Debian Debian Linux=10.0
debian/python-pysaml2
6.5.1-17.0.1-27.5.0-47.5.4-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/pysaml2 to a version that resolves this vulnerability.

    Fixed in 5.0.0
  2. Upgrade

    Upgrade debian/python-pysaml2 to a version that resolves this vulnerability.

    Fixed in 6.5.1-1Fixed in 7.0.1-2Fixed in 7.5.0-4Fixed in 7.5.4-2
  3. Upgrade

    Upgrade pysaml2 to a version that resolves this vulnerability.

    Fixed in 5.0.0

Event History

Jan 13, 2020
CVE Published
via MITRE·06:11 PM
Data Sourced
via MITRE·06:11 PM
Description
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 6, 2020
Advisory Published
via GitHub·07:41 PM
Jan 11, 2024
Data Sourced
via Launchpad·11:51 PM
Description
Feb 23, 2026
Data Sourced
via Ubuntu·11:52 PM
RemedyDescriptionSeverityAffected Software
Jul 7, 2026
Data Sourced
via Debian·03:58 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2020-5390?

CVE-2020-5390 has a high severity rating due to its potential to enable XML Signature Wrapping attacks.

2

How do I fix CVE-2020-5390?

To fix CVE-2020-5390, upgrade PySAML2 to version 5.0.0 or later.

3

Which versions of PySAML2 are affected by CVE-2020-5390?

CVE-2020-5390 affects all versions of PySAML2 prior to 5.0.0.

4

Is CVE-2020-5390 present in Debian or Ubuntu distributions?

Yes, CVE-2020-5390 is present in various Debian and Ubuntu distributions that utilize vulnerable versions of PySAML2.

5

What is the impact of exploiting CVE-2020-5390?

Exploiting CVE-2020-5390 could allow attackers to manipulate SAML signatures, potentially leading to unauthorized access.

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