PatchTheCVEpysaml2 project vulnerabilities
Recent CVEs affecting pysaml2 project products. 5 tracked.
pysaml2 project has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 4. Most recent: 2020-01-13. Highest priority: CVE-2017-1000433 (score 60/100).
- CVE-2020-5390 HIGH 7.5 UPGRADE MITIGATE PySAML2 before 5.0.0 does not check that the signature in a SAML document is enveloped and thus signature wrap
- CVE-2017-1000433 HIGH 8.1 UPGRADE MITIGATE pysaml2 version 4.4.0 and older accept any password when run with python optimizations enabled
- CVE-2017-1000246 MEDIUM 5.3 UPGRADE Python package pysaml2 version 4.4.0 and earlier reuses the initialization vector across encryptions in the ID
- CVE-2016-10149 HIGH 7.5 UPGRADE MITIGATE XML External Entity (XXE) vulnerability in PySAML2 4.4.0 and earlier allows remote attackers to read arbitrary
- CVE-2016-10127 CRITICAL 9.0 MITIGATE PySAML2 allows remote attackers to conduct XML external entity (XXE) attacks via a crafted SAML XML request or
FAQ
How do I fix pysaml2 project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is pysaml2 project being exploited right now?
None of the tracked pysaml2 project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pysaml2 project CVE should I patch first?
CVE-2017-1000433 currently ranks highest (60/100): pysaml2 version 4.4.0 and older accept any password when run with python optimizations enabled.