Поиск уязвимостей
Количество 20
Количество 20
ALT-PU-2023-1534
ALT-PU-2023-1534: package `python3-module-pysaml2` update to version 7.4.1-alt1
ALT-PU-2023-1286
ALT-PU-2023-1286: package `python3-module-pysaml2` update to version 7.4.0-alt1
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 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.
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 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.
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 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.
CVE-2020-5390
PySAML2 before 5.0.0 does not check that the signature in a SAML docum ...
GHSA-qf7v-8hj3-4xw7
Improper Verification of Cryptographic Signature in PySAML2
BDU:2020-05775
Уязвимость библиотеки для обмена идентификационными данными по стандарту SAML2 PySAML2, связанная с некорректным подтверждением криптографической подписи данных, позволяющая нарушителю обойти проверку подписи и получить доступ к защищаемой информации
CVE-2021-21239
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.
CVE-2021-21239
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.
CVE-2021-21239
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.
CVE-2021-21239
PySAML2 is a pure python implementation of SAML Version 2 Standard. Py ...
CVE-2021-21238
PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0.
CVE-2021-21238
PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0.
CVE-2021-21238
PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0.
CVE-2021-21238
PySAML2 is a pure python implementation of SAML Version 2 Standard. Py ...
GHSA-5p3x-r448-pc62
Improper Verification of Cryptographic Signature in PySAML2
GHSA-f4g9-h89h-jgv9
SAML XML Signature wrapping in PySAML2
BDU:2024-02841
Уязвимость библиотеки для обмена идентификационными данными по стандарту SAML2 PySAML2, связанная с неправильной проверкой криптографической подписи, позволяющая нарушителю обойти проверку подписи и получить доступ к защищаемой информации
ROS-20240410-12
Уязвимость python3-pysaml2
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
ALT-PU-2023-1534 ALT-PU-2023-1534: package `python3-module-pysaml2` update to version 7.4.1-alt1 | CVSS3: 7.5 | больше 3 лет назад | ||
ALT-PU-2023-1286 ALT-PU-2023-1286: package `python3-module-pysaml2` update to version 7.4.0-alt1 | CVSS3: 7.5 | больше 3 лет назад | ||
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 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. | CVSS3: 7.5 | 1% Низкий | почти 7 лет назад | |
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 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. | CVSS3: 7.5 | 1% Низкий | почти 7 лет назад | |
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 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. | CVSS3: 7.5 | 1% Низкий | почти 7 лет назад | |
CVE-2020-5390 PySAML2 before 5.0.0 does not check that the signature in a SAML docum ... | CVSS3: 7.5 | 1% Низкий | почти 7 лет назад | |
GHSA-qf7v-8hj3-4xw7 Improper Verification of Cryptographic Signature in PySAML2 | CVSS3: 7.5 | 1% Низкий | больше 6 лет назад | |
BDU:2020-05775 Уязвимость библиотеки для обмена идентификационными данными по стандарту SAML2 PySAML2, связанная с некорректным подтверждением криптографической подписи данных, позволяющая нарушителю обойти проверку подписи и получить доступ к защищаемой информации | CVSS3: 7.5 | 1% Низкий | почти 7 лет назад | |
CVE-2021-21239 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. | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
CVE-2021-21239 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. | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
CVE-2021-21239 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. | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
CVE-2021-21239 PySAML2 is a pure python implementation of SAML Version 2 Standard. Py ... | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
CVE-2021-21238 PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0. | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
CVE-2021-21238 PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0. | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
CVE-2021-21238 PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0. | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
CVE-2021-21238 PySAML2 is a pure python implementation of SAML Version 2 Standard. Py ... | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
GHSA-5p3x-r448-pc62 Improper Verification of Cryptographic Signature in PySAML2 | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
GHSA-f4g9-h89h-jgv9 SAML XML Signature wrapping in PySAML2 | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
BDU:2024-02841 Уязвимость библиотеки для обмена идентификационными данными по стандарту SAML2 PySAML2, связанная с неправильной проверкой криптографической подписи, позволяющая нарушителю обойти проверку подписи и получить доступ к защищаемой информации | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад | |
ROS-20240410-12 Уязвимость python3-pysaml2 | CVSS3: 6.5 | 1% Низкий | больше 2 лет назад |
Уязвимостей на страницу