ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2020-0601

Microsoft Windows CryptoAPI Spoofing Vulnerability

Published Jan 14, 2020 · catalog updated Jun 16, 2026 · Microsoft Windows

Patch now

CVE-2020-0601 is in the CISA known-exploited catalog, due May 3, 2022. Confirm Microsoft Windows against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
Severity
High8.1
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
89.44%
Remediation
Remediation guidance
Affected products
cpe golang/go · cpe microsoft/windows 10 1507 · cpe microsoft/windows 10 1607 · cpe microsoft/windows 10 1709 · cpe microsoft/windows 10 1803 · vendor Microsoft Windows

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe golang/goversion unspecified
  • cpe microsoft/windows 10 1507version unspecified
  • cpe microsoft/windows 10 1607version unspecified
  • cpe microsoft/windows 10 1709version unspecified
  • cpe microsoft/windows 10 1803version unspecified
  • vendor Microsoft Windowsversion unspecified

How to fix CVE-2020-0601

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2020-0601 is in the CISA known-exploited catalog, due May 3, 2022. Confirm Microsoft Windows against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Which versions are affected?

Affected version ranges are not on this record. Apply updates per vendor instructions.

What should an analyst verify?

CWE-295: Improper Certificate Validation. EPSS 89.44%. The CISA KEV listing is the exploitation evidence. A public exploit reference is linked in Sources. That is not the same as confirmed exploitation. Use the source links for the original advisory.

Technology hubs

Windows security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 14, 2020 · Catalog

    Detected

    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-i

  2. Nov 3, 2021 · CISA KEV

    Known exploited

    Apply updates per vendor instructions.

  3. May 3, 2022 · CISA KEV

    Remediation due

    Apply updates per vendor instructions.

  4. Jun 16, 2026 · Catalog

    Updated

    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-i

Sources

  • CISA KEVConfirmed exploitationCVE-2020-0601

    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-i

    cisa.gov
  • CVE.orgVulnerability recordCVE-2020-0601

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2020-0601

    30-day exploitation probability 89.4%

    first.org
  • Exploit DatabasePublic exploit reference47933

    Public archive entry. The exploit body is not stored here.

    exploit-db.com
  • NIST NVDVulnerability recordCVE-2020-0601

    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 wa

    nvd.nist.gov
  • Packet Storm SecurityCited referencehttp://packetstormsecurity.com/files/155960/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept.html

    Packet Storm link already published on the finding.

    packetstormsecurity.com
  • Packet Storm SecurityCited referencehttp://packetstormsecurity.com/files/155961/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept.html

    Packet Storm link already published on the finding.

    packetstormsecurity.com
  • VulnCheck KEVConfirmed exploitationCVE-2020-0601

    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 ap

    vulncheck.com

References

Freshness

Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.