![]() |
Home ▼ Bookkeeping
Online ▼ Security
Audits ▼
Managed
DNS ▼
About
Order
FAQ
Acceptable Use Policy
Dynamic DNS Clients
Configure Domains Dyanmic DNS Update Password Network
Monitor ▼
Enterprise Package
Advanced Package
Standard Package
Free Trial
FAQ
Price/Feature Summary
Order/Renew
Examples
Configure/Status Alert Profiles | ||
CVE ID: | CVE-2021-21239 |
Description: | PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. Users of pysaml2 that use the default CryptoBackendXmlSec1 backend and need to verify signed SAML documents are impacted. PySAML2 does not ensure that a signed SAML document is correctly signed. The default CryptoBackendXmlSec1 backend is using the xmlsec1 binary to verify the signature of signed SAML documents, but by default xmlsec1 accepts any type of key found within the given document. xmlsec1 needs to be configured explicitly to only use only _x509 certificates_ for the verification process of the SAML document signature. This is fixed in PySAML2 6.5.0. |
Test IDs: | 1.3.6.1.4.1.25623.1.0.845051 1.3.6.1.4.1.25623.1.1.12.2021.5066.2 1.3.6.1.4.1.25623.1.0.892577 |
Cross References: |
Common Vulnerability Exposure (CVE) ID: CVE-2021-21239 https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62 https://github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99 https://github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99 https://github.com/IdentityPython/pysaml2/releases/tag/v6.5.0 https://github.com/IdentityPython/pysaml2/releases/tag/v6.5.0 https://pypi.org/project/pysaml2 https://pypi.org/project/pysaml2 https://www.aleksey.com/pipermail/xmlsec/2013/009717.html https://www.aleksey.com/pipermail/xmlsec/2013/009717.html https://lists.debian.org/debian-lts-announce/2021/02/msg00038.html |