CVE-2020-5390: Improper Verification of Cryptographic Signature in PySAML2
(updated )
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.
References
- github.com/IdentityPython/pysaml2
- github.com/IdentityPython/pysaml2/blob/master/CHANGELOG.md
- github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25
- github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e
- github.com/IdentityPython/pysaml2/releases
- github.com/IdentityPython/pysaml2/releases/tag/v5.0.0
- github.com/advisories/GHSA-qf7v-8hj3-4xw7
- github.com/pypa/advisory-database/tree/main/vulns/pysaml2/PYSEC-2020-94.yaml
- lists.debian.org/debian-lts-announce/2020/02/msg00025.html
- nvd.nist.gov/vuln/detail/CVE-2020-5390
- pypi.org/project/pysaml2/5.0.0
- usn.ubuntu.com/4245-1
- www.debian.org/security/2020/dsa-4630
Detect and mitigate CVE-2020-5390 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →