CVE-2020-5390

unknown
Published 2020-05-06 ยท Modified 2023-11-08
CVSS v3
โ€”
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
โ€”

Description

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.

Predictions

Exploit likelihood
30%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

suse SUSE Affected 1 release
VersionStatusFixed in
โ€” Affected โ€”
debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 4.5.0-7
sid Fixed 4.5.0-7
forky Fixed 4.5.0-7
bullseye Fixed 4.5.0-7
bookworm Fixed 4.5.0-7

Package impact

EcosystemPackageVulnerableFixed
python PyPIpysaml2<5.0.05.0.0
python PyPIpysaml2<5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25||<5.0.0f27c7e7a7010f83380566a219fd6a290a00f2b6e

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.