Live › vulnerability › CVE-2020-0601
Go to dashboardWindows CryptoAPI (Crypt32.dll) incorrectly validates ECC certificates, so a forged certificate passes as trusted. An attacker can sign malware so it looks like it came from a legitimate publisher, or intercept and decrypt connections that rely on the bad check.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply updates per vendor instructions.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Microsoft Windows | vendor | – | – |
Unknown from the sources. In the analyst’s queue.
Apply the Microsoft security update for CVE-2020-0601 per vendor instructions (CISA KEV required action).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
CISA required action: Apply updates per vendor instructions.
This page as .md · .json · in your agent: get_signal("CVE-2020-0601")
CISA KEV catalog, Creative Commons 0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.