| Title | PySAML2 におけるデジタル署名の検証に関する脆弱性 |
|---|---|
| Summary | PySAML2 には、デジタル署名の検証に関する脆弱性が存在します。 |
| Possible impacts | 情報を改ざんされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | Jan. 20, 2021, midnight |
| Registration Date | Oct. 6, 2021, 6:05 p.m. |
| Last Update | Oct. 6, 2021, 6:05 p.m. |
| CVSS3.0 : 警告 | |
| Score | 6.5 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| CVSS2.0 : 警告 | |
| Score | 4.3 |
|---|---|
| Vector | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| Debian |
| Debian GNU/Linux |
| PySAML2 project |
| PySAML2 6.5.0 未満 |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2021年10月06日] 掲載 |
Oct. 6, 2021, 6:05 p.m. |
| Summary | 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. |
|---|---|
| Publication Date | Jan. 22, 2021, 12:15 a.m. |
| Registration Date | Jan. 26, 2021, 10:40 a.m. |
| Last Update | Nov. 21, 2024, 2:47 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:pysaml2_project:pysaml2:*:*:*:*:*:*:*:* | 6.5.0 | ||||
| Configuration2 | or higher | or less | more than | less than | |
| cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:* | |||||