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).
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2017-2629 from the MITRE CVE dictionary dictionary and NIST NVD.
NOTE: The following CVSS v3 metrics and score provided are preliminary and subject to review.
| CVSS3 Base Score | 4.3 |
|---|---|
| CVSS3 Base Metrics | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | Required |
| Scope | Unchanged |
| Confidentiality | None |
| Integrity Impact | Low |
| Availability Impact | None |
| Platform | Package | State |
|---|---|---|
| Red Hat Software Collections for Red Hat Enterprise Linux | httpd24-curl | Not affected |
| Red Hat JBoss Web Server 3 | curl | Not affected |
| Red Hat Enterprise Linux 7 | curl | Not affected |
| Red Hat Enterprise Linux 6 | curl | Not affected |
| Red Hat Enterprise Linux 5 | curl | Not affected |
| RHEV Manager 3 | mingw-virt-viewer | Not affected |
| .NET Core 2.0 on Red Hat Enterprise Linux | rh-dotnet20-curl | Not affected |
| .NET Core 1.0 on Red Hat Enterprise Linux | rh-dotnetcore10-curl | Not affected |
| .NET Core 1.0 on Red Hat Enterprise Linux | rh-dotnetcore11-curl | Not affected |
Vulmon