CVE-2020-5390
Published: 13 January 2020
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.
Priority
Status
Package | Release | Status |
---|---|---|
python-pysaml2 Launchpad, Ubuntu, Debian |
bionic |
Released
(4.0.2-0ubuntu3.1)
|
disco |
Released
(4.5.0+dfsg1-0ubuntu2.19.04.1)
|
|
eoan |
Released
(4.5.0+dfsg1-0ubuntu2.19.10.1)
|
|
trusty |
Does not exist
|
|
upstream |
Needs triage
|
|
xenial |
Released
(3.0.0-3ubuntu1.16.04.4)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.5 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | High |
Availability impact | None |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
References
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5390
- https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25 (v5.0.0)
- https://github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e
- https://github.com/IdentityPython/pysaml2/releases
- https://github.com/IdentityPython/pysaml2/releases/tag/v5.0.0
- https://pypi.org/project/pysaml2/5.0.0/
- https://ubuntu.com/security/notices/USN-4245-1
- NVD
- Launchpad
- Debian