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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2119-1 | python-pysaml2 security update |
Debian DSA |
DSA-4630-1 | python-pysaml2 security update |
EUVD |
EUVD-2020-0157 | 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. |
Github GHSA |
GHSA-qf7v-8hj3-4xw7 | Improper Verification of Cryptographic Signature in PySAML2 |
Ubuntu USN |
USN-4245-1 | PySAML2 vulnerability |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T08:30:23.936Z
Reserved: 2020-01-03T00:00:00
Link: CVE-2020-5390
No data.
Status : Modified
Published: 2020-01-13T19:15:12.413
Modified: 2024-11-21T05:34:02.957
Link: CVE-2020-5390
OpenCVE Enrichment
No data.
Weaknesses
Debian DLA
Debian DSA
EUVD
Github GHSA
Ubuntu USN