Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2021-22890 | First vendor Publication | 2021-04-01 |
Vendor | Cve | Last vendor Modification | 2024-03-27 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | |||
---|---|---|---|
Overall CVSS Score | 3.7 | ||
Base Score | 3.7 | Environmental Score | 3.7 |
impact SubScore | 1.4 | Temporal Score | 3.7 |
Exploitabality Sub Score | 2.2 | ||
Attack Vector | Network | Attack Complexity | High |
Privileges Required | None | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | Low | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:N/AC:M/Au:N/C:N/I:P/A:N) | |||
---|---|---|---|
Cvss Base Score | 4.3 | Attack Range | Network |
Cvss Impact Score | 2.9 | Attack Complexity | Medium |
Cvss Expoit Score | 8.6 | Authentication | None Required |
Calculate full CVSS 2.0 Vectors scores |
Detail
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. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22890 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-290 | Authentication Bypass by Spoofing |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2024-03-27 17:28:11 |
|
2023-11-07 21:35:18 |
|
2022-10-07 02:05:25 |
|
2022-04-06 21:23:13 |
|
2022-03-10 21:23:24 |
|
2021-08-05 01:42:11 |
|
2021-07-21 05:23:00 |
|
2021-05-27 21:23:18 |
|
2021-05-26 21:23:19 |
|
2021-05-21 13:23:01 |
|
2021-05-04 14:08:46 |
|
2021-04-22 09:22:48 |
|
2021-04-22 03:13:49 |
|
2021-04-07 01:36:52 |
|
2021-04-07 01:36:26 |
|
2021-04-07 00:22:57 |
|
2021-04-06 09:22:56 |
|
2021-04-04 09:22:54 |
|
2021-04-02 00:22:58 |
|