CVE-2020-5390: 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…
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: python-pysaml2 (Debian:10) 4.5.0-4+deb10u1; python-pysaml2 (Debian:12) 4.5.0-7; python-pysaml2 (Debian:8) 2.0.0-1+deb8u3.
Low priority for now. Upgrade to python-pysaml2 (Debian:10) 4.5.0-4+deb10u1; python-pysaml2 (Debian:12) 4.5.0-7; python-pysaml2 (Debian:8) 2.0.0-1+deb8u3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 13, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 69th percentile
- CWE
- CWE-347
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pysaml2 project | pysaml2 | cpe:2.3:a:pysaml2_project:pysaml2 |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.04
- canonical ubuntu linux19.10
- debian debian linux10.0
- debian debian linux8.0
- debian debian linux9.0
- pysaml2 project pysaml2before 5.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | python-pysaml2 | before 4.5.0-4+deb10u1 | 4.5.0-4+deb10u1 |
| Debian:12 | python-pysaml2 | before 4.5.0-7 | 4.5.0-7 |
| Debian:8 | python-pysaml2 | before 2.0.0-1+deb8u3 | 2.0.0-1+deb8u3 |
| Debian:9 | python-pysaml2 | before 3.0.0-5+deb9u1 | 3.0.0-5+deb9u1 |
| openSUSE:Tumbleweed | python-pysaml2 | before 7.4.2-1.2 | 7.4.2-1.2 |
| openSUSE:Tumbleweed | python-pysaml2 | before 7.5.4-1.1 | 7.5.4-1.1 |
| PyPI | pysaml2 | before 5.0.0 | 5.0.0 |
| SUSE:OpenStack Cloud 9 | ardana-cassandra | before 9.0+git.1600802664.7e480a2-3.6.2 | 9.0+git.1600802664.7e480a2-3.6.2 |
| SUSE:OpenStack Cloud 9 | ardana-mq | before 9.0+git.1605174486.a78ddce-3.19.2 | 9.0+git.1605174486.a78ddce-3.19.2 |
| SUSE:OpenStack Cloud 9 | ardana-osconfig | before 9.0+git.1601621747.a87e5a0-3.22.2 | 9.0+git.1601621747.a87e5a0-3.22.2 |
| SUSE:OpenStack Cloud 9 | ardana-tempest | before 9.0+git.1603378983.fc0bca9-3.19.2 | 9.0+git.1603378983.fc0bca9-3.19.2 |
| SUSE:OpenStack Cloud 9 | grafana | before 6.7.4-3.20.1 | 6.7.4-3.20.1 |
| SUSE:OpenStack Cloud 9 | influxdb | before 1.3.8-4.3.3 | 1.3.8-4.3.3 |
| SUSE:OpenStack Cloud 9 | openstack-cinder | before 13.0.10~dev20-3.28.2 | 13.0.10~dev20-3.28.2 |
| SUSE:OpenStack Cloud 9 | openstack-heat | before 11.0.4~dev4-3.19.2 | 11.0.4~dev4-3.19.2 |
| SUSE:OpenStack Cloud 9 | openstack-heat-gbp | before 12.0.1~dev2-3.3.4 | 12.0.1~dev2-3.3.4 |
| SUSE:OpenStack Cloud 9 | openstack-heat-templates | before 0.0.0+git.1605509190.64f020b6-3.9.3 | 0.0.0+git.1605509190.64f020b6-3.9.3 |
| SUSE:OpenStack Cloud 9 | openstack-horizon-plugin-gbp-ui | before 12.0.1~dev3-3.3.4 | 12.0.1~dev3-3.3.4 |
| SUSE:OpenStack Cloud 9 | openstack-ironic-python-agent | before 3.3.4~dev6-3.19.4 | 3.3.4~dev6-3.19.4 |
| SUSE:OpenStack Cloud 9 | openstack-manila | before 7.4.2~dev57-4.30.2 | 7.4.2~dev57-4.30.2 |
| SUSE:OpenStack Cloud 9 | openstack-neutron | before 13.0.8~dev135-3.31.2 | 13.0.8~dev135-3.31.2 |
| SUSE:OpenStack Cloud 9 | openstack-neutron-gbp | before 12.0.1~dev5-3.19.4 | 12.0.1~dev5-3.19.4 |
| SUSE:OpenStack Cloud 9 | openstack-neutron-vpnaas | before 13.0.2~dev6-3.9.2 | 13.0.2~dev6-3.9.2 |
| SUSE:OpenStack Cloud 9 | openstack-nova | before 18.3.1~dev77-3.31.2 | 18.3.1~dev77-3.31.2 |
+25
Same product
pysaml2 project: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-10127PySAML2 allows remote attackers to conduct XML external entity (XXE) attacks via a crafted SAML XML request or response.37Monitor
- CVE-2017-1000433pysaml2 version 4.4.0 and older accept any password when run with python optimizations enabled.33Monitor
- CVE-2016-10149XML External Entity (XXE) vulnerability in PySAML2 4.4.0 and earlier allows remote attackers to read arbitrary files via a crafted SAML XML…32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-1000246Nov 17, 2017 · Python package pysaml2 version 4.4.0 and earlier reuses the initialization vector across encryptions in the IDP server, resulting in weak…21Monitor
- Later →CVE-2021-21238Jan 21, 2021 · SAML XML Signature wrapping26Monitor
- Later →CVE-2021-21239Jan 21, 2021 · Open default xmlsec1 key-type preference26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:python-pysaml2 | 4.5.0-7 · Debian:12 | Package registry (OSV) |
| opensuse:python-pysaml2 | 7.4.2-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:pysaml2 | 5.0.0 | Package registry (OSV) |
| suse:ardana-cassandra | 9.0+git.1600802664.7e480a2-3.6.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:ardana-mq | 9.0+git.1605174486.a78ddce-3.19.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:ardana-osconfig | 9.0+git.1601621747.a87e5a0-3.22.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:ardana-tempest | 9.0+git.1603378983.fc0bca9-3.19.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:grafana | 6.7.4-3.20.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:influxdb | 1.3.8-4.3.3 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-cinder | 13.0.10~dev20-3.28.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-heat | 11.0.4~dev4-3.19.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-heat-gbp | 12.0.1~dev2-3.3.4 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-heat-templates | 0.0.0+git.1605509190.64f020b6-3.9.3 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-horizon-plugin-gbp-ui | 12.0.1~dev3-3.3.4 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-ironic-python-agent | 3.3.4~dev6-3.19.4 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e
- github.com/IdentityPython/pysaml2/releases
- github.com/IdentityPython/pysaml2/releases/tag/v5.0.0
- lists.debian.org/debian-lts-announce/2020/02/msg00025.html
- pypi.org/project/pysaml2/5.0.0/
- usn.ubuntu.com/4245-1/
- www.debian.org/security/2020/dsa-4630
Vendor advisories and official records. Exploit/PoC links are deliberately left out.