| Title | curl における証明書検証に関する脆弱性 |
|---|---|
| Summary | curl には、証明書検証に関する脆弱性が存在します。 |
| Possible impacts | 情報を改ざんされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | Feb. 22, 2017, midnight |
| Registration Date | Oct. 17, 2018, 12:08 p.m. |
| Last Update | Oct. 17, 2018, 12:08 p.m. |
| CVSS3.0 : 警告 | |
| Score | 6.5 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| CVSS2.0 : 警告 | |
| Score | 4 |
|---|---|
| Vector | AV:N/AC:L/Au:S/C:N/I:P/A:N |
| Haxx |
| cURL 7.53.0 未満 |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2018年10月17日] 掲載 |
Oct. 17, 2018, 12:08 p.m. |
| Summary | curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server's certificate's validity in the code that checks for a test success or failure. It ends up always thinking there's valid proof, even when there is none or if the server doesn't support the TLS extension in question. This could lead to users not detecting when a server's certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status). |
|---|---|
| Publication Date | July 28, 2018, 4:29 a.m. |
| Registration Date | Jan. 26, 2021, 1:22 p.m. |
| Last Update | Nov. 21, 2024, 12:23 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:* | 7.53.0 | ||||