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.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Configuration 6 (hide)
|
Configuration 7 (hide)
|
Configuration 8 (hide)
|
History
No history.
Information
Published : 2021-04-01 18:15
Updated : 2024-11-21 05:50
NVD link : CVE-2021-22890
Mitre link : CVE-2021-22890
CVE.ORG link : CVE-2021-22890
JSON object : View
Products Affected
netapp
- hci_storage_node
- hci_management_node
- solidfire
oracle
- communications_billing_and_revenue_management
- essbase
splunk
- universal_forwarder
debian
- debian_linux
fedoraproject
- fedora
siemens
- sinec_infrastructure_network_services
haxx
- libcurl
broadcom
- fabric_operating_system