Уязвимость атаки типа "человек посередине" из-за неправильной обработки тикетов сеанса TLS 1.3 в curl
Описание
В версиях curl с 7.63.0 по 7.75.0 (включительно) существует уязвимость, которая позволяет злоумышленному HTTPS-прокси выполнить атаку "человек посередине" (MITM) из-за неправильной обработки тикетов сеанса TLS 1.3. При использовании HTTPS-прокси и TLS 1.3 библиотека libcurl может путать тикеты сеанса, поступающие от HTTPS-прокси, с тикетами, поступающими от удалённого сервера, и ошибочно считать, что хост уже прошёл handshake. Из-за этой путаницы HTTPS-прокси может обмануть libcurl, заставив его использовать неправильный тикет сеанса для хоста, что позволяет обойти проверку TLS-сертификата сервера и сделать атаку MITM незаметной. Для выполнения атаки такое вредоносное HTTPS-прокси должно предоставить сертификат, который curl примет для атакуемого сервера, если только curl не настроен игнорировать проверку сертификата сервера.
Затронутые версии ПО
- curl версии с 7.63.0 до 7.75.0 включительно
Тип уязвимости
Атака MITM (man-in-the-middle)
Ссылки
- PatchThird Party Advisory
- PatchVendor Advisory
- ExploitIssue TrackingPatchThird Party Advisory
- Mailing ListThird Party Advisory
- Mailing ListThird Party Advisory
- Mailing ListThird Party Advisory
- Third Party Advisory
- Third Party Advisory
- Third Party Advisory
- PatchThird Party Advisory
- PatchVendor Advisory
- ExploitIssue TrackingPatchThird Party Advisory
- Mailing ListThird Party Advisory
- Mailing ListThird Party Advisory
- Mailing ListThird Party Advisory
- Third Party Advisory
- Third Party Advisory
- Third Party Advisory
Уязвимые конфигурации
Одно из
Одно из
Одно из
Одно из
EPSS
3.7 Low
CVSS3
4.3 Medium
CVSS3
4.3 Medium
CVSS2
Дефекты
Связанные уязвимости
curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived from the remote server and then wrongly "short-cut" the host handshake. When confusing the tickets, a HTTPS proxy can trick libcurl to use the wrong session ticket resume for the host and thereby circumvent the server TLS certificate check and make a MITM attack to be possible to perform unnoticed. Note that such a malicious HTTPS proxy needs to provide a certificate that curl will accept for the MITMed server for an attack to work - unless curl has been told to ignore the server certificate check.
curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived from the remote server and then wrongly "short-cut" the host handshake. When confusing the tickets, a HTTPS proxy can trick libcurl to use the wrong session ticket resume for the host and thereby circumvent the server TLS certificate check and make a MITM attack to be possible to perform unnoticed. Note that such a malicious HTTPS proxy needs to provide a certificate that curl will accept for the MITMed server for an attack to work - unless curl has been told to ignore the server certificate check.
curl 7.63.0 to and including 7.75.0 includes vulnerability that allows ...
curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived from the remote server and then wrongly "short-cut" the host handshake. When confusing the tickets, a HTTPS proxy can trick libcurl to use the wrong session ticket resume for the host and thereby circumvent the server TLS certificate check and make a MITM attack to be possible to perform unnoticed. Note that such a malicious HTTPS proxy needs to provide a certificate that curl will accept for the MITMed server for an attack to work - unless curl has been told to ignore the server certificate check.
EPSS
3.7 Low
CVSS3
4.3 Medium
CVSS3
4.3 Medium
CVSS2