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.
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
| Link | Tags |
|---|---|
| https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25 | third party advisory patch |
| https://github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e | third party advisory patch |
| https://github.com/IdentityPython/pysaml2/releases/tag/v5.0.0 | third party advisory release notes |
| https://github.com/IdentityPython/pysaml2/releases | third party advisory release notes |
| https://pypi.org/project/pysaml2/5.0.0/ | third party advisory product |
| https://usn.ubuntu.com/4245-1/ | third party advisory vendor advisory |
| https://www.debian.org/security/2020/dsa-4630 | third party advisory vendor advisory |
| https://lists.debian.org/debian-lts-announce/2020/02/msg00025.html | third party advisory mailing list |