| Title | curl および libcurl における証明書検証に関する脆弱性 |
|---|---|
| Summary | curl および libcurl には、証明書検証に関する脆弱性が存在します。 |
| Possible impacts | 情報を改ざんされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | April 19, 2017, midnight |
| Registration Date | Oct. 16, 2018, 1:37 p.m. |
| Last Update | Oct. 16, 2018, 1:37 p.m. |
| CVSS3.0 : 重要 | |
| Score | 7.5 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CVSS2.0 : 警告 | |
| Score | 5 |
|---|---|
| Vector | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| Haxx |
| libcurl |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2018年10月16日] 掲載 |
Oct. 16, 2018, 1:37 p.m. |
| Summary | In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was established by the previous certificate (or no certificate). libcurl supports by default the use of TLS session id/ticket to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason an existing TLS connection couldn't be kept alive to make the next handshake faster. This flaw is a regression and identical to CVE-2016-5419 reported on August 3rd 2016, but affecting a different version range. |
|---|---|
| Publication Date | July 16, 2018, 10:29 p.m. |
| Registration Date | Jan. 26, 2021, 1:28 p.m. |
| Last Update | Nov. 21, 2024, 12:31 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:haxx:libcurl:*:*:*:*:*:*:*:* | 7.52.0 | 7.53.1 | |||