CVE-2020-0601
HIGHCISA KEVEPSS 100th pctlDescription
A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates.An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source, aka 'Windows CryptoAPI Spoofing Vulnerability'.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Exploit Intelligence
Very high risk: more likely to be exploited than 100% of all known CVEs.
Microsoft Windows CryptoAPI Spoofing Vulnerability
Microsoft Windows CryptoAPI (Crypt32.dll) contains a spoofing vulnerability in the way it validates Elliptic Curve Cryptography (ECC) certificates. An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source. A successful exploit could also allow the attacker to conduct man-in-the-middle attacks and decrypt confidential information on user connections to the affected software. The vulnerability is also known under the moniker of CurveBall.
Apply updates per vendor instructions.
Remediation due: 2022-05-03
References
Related Vulnerabilities
Other CWE-295 (Improper Certificate Validation) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2015-4000 | Low | 3.7 | 100% | - | Fix |
| CVE-2009-3555 | Critical | 9.8 | 87% | - | Fix |
| CVE-2022-26923 | High | 8.8 | 83% | KEV | Fix |
| CVE-2023-27823 | Critical | 9.8 | 53% | - | - |
| CVE-2022-42979 | High | 8.8 | 24% | - | - |
| CVE-2018-8034 | High | 7.5 | 21% | - | Fix |
Common questions
How do I fix CVE-2020-0601?
Upgrade Go Programming Language to 1.12.16 or later.
Is CVE-2020-0601 being actively exploited?
Yes. CVE-2020-0601 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2022-05-03. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2020-0601?
CVE-2020-0601 has a CVSS v3 base score of 8.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2020-0601 affect?
Published advisories record a fix for Go Programming Language (Windows application). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2020-0601
Markdown
[](https://tridentstack.com/cve/CVE-2020-0601)HTML
<a href="https://tridentstack.com/cve/CVE-2020-0601"><img src="https://tridentstack.com/cve/badge/CVE-2020-0601.svg" alt="CVE-2020-0601"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-12-18.