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.
Weakness
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Pysaml2 | Pysaml2_project | * | 5.0.0 (excluding) |
| Python-pysaml2 | Ubuntu | bionic | * |
| Python-pysaml2 | Ubuntu | devel | * |
| Python-pysaml2 | Ubuntu | disco | * |
| Python-pysaml2 | Ubuntu | eoan | * |
| Python-pysaml2 | Ubuntu | esm-infra/bionic | * |
| Python-pysaml2 | Ubuntu | esm-infra/xenial | * |
| Python-pysaml2 | Ubuntu | trusty | * |
| Python-pysaml2 | Ubuntu | xenial | * |
Related Attack Patterns
References
- https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25
- https://github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e
- https://github.com/IdentityPython/pysaml2/releases
- https://github.com/IdentityPython/pysaml2/releases/tag/v5.0.0
- https://lists.debian.org/debian-lts-announce/2020/02/msg00025.html
- https://pypi.org/project/pysaml2/5.0.0/
- https://usn.ubuntu.com/4245-1/
- https://www.debian.org/security/2020/dsa-4630
- https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25
- https://github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e
- https://github.com/IdentityPython/pysaml2/releases
- https://github.com/IdentityPython/pysaml2/releases/tag/v5.0.0
- https://lists.debian.org/debian-lts-announce/2020/02/msg00025.html
- https://pypi.org/project/pysaml2/5.0.0/
- https://usn.ubuntu.com/4245-1/
- https://www.debian.org/security/2020/dsa-4630