CVE-2020-0601

Microsoft Windows CryptoAPI Spoofing

8.1 HIGHActively exploited (CISA KEV)EPSS 89.4%

Published14 Jan 2020
Added to CISA KEV3 Nov 2021
Remediation due3 May 2022

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.

Added to KEV: 3 Nov 2021Federal remediation due: 3 May 2022

Description

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'.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected products

Golang Go≥ 1.12 < 1.12.16 · ≥ 1.13 < 1.13.7

Microsoft Windows 10 1507all versions

Microsoft Windows 10 1607all versions

Microsoft Windows 10 1709all versions

Microsoft Windows 10 1803all versions

Microsoft Windows 10 1809all versions

Microsoft Windows 10 1903all versions

Microsoft Windows 10 1909all versions

Microsoft Windows Server 1803all versions

Microsoft Windows Server 1903all versions

Microsoft Windows Server 1909all versions

Microsoft Windows Server 2016all versions

Microsoft Windows Server 2019all versions

Remediation

Fixed in

Golang Go≥ 1.12.16

Patch & vendor advisories

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601

References

http://packetstormsecurity.com/files/155960/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept.htmlThird Party AdvisoryVDB Entry
http://packetstormsecurity.com/files/155961/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept.htmlThird Party AdvisoryVDB Entry
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601PatchVendor Advisory
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-0601US Government Resource

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2020-0601 being actively exploited?

Yes. CVE-2020-0601 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 3 Nov 2021.

How severe is CVE-2020-0601?

CVE-2020-0601 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 89.4% probability of exploitation.

Which products are affected by CVE-2020-0601?

Affected products include Golang Go, Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1709, Microsoft Windows 10 1803, and 8 more.

How do I fix CVE-2020-0601?

Upgrade affected software to a fixed version, for example Golang Go 1.12.16 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2020-0601 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.