CVE-2021-21239 - log back

CVE-2021-21239 edited at 23 Jan 2021 04:07:24
References
https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62
https://github.com/IdentityPython/pysaml2/commit/751dbf50a51131b13d55989395f9b115045f9737
+ https://www.aleksey.com/pipermail/xmlsec/2013/009717.html
+ https://nvd.nist.gov/vuln/detail/CVE-2021-21239
CVE-2021-21239 edited at 21 Jan 2021 18:14:42
Severity
- Medium
+ Critical
CVE-2021-21239 edited at 21 Jan 2021 18:11:20
Severity
- Unknown
+ Medium
Remote
- Unknown
+ Local
Type
- Unknown
+ Signature forgery
Description
+ 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.
References
+ https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62
+ https://github.com/IdentityPython/pysaml2/commit/751dbf50a51131b13d55989395f9b115045f9737
Notes
CVE-2021-21239 created at 21 Jan 2021 18:08:16