Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Windows CryptoAPI Spoofing Vulnerability

Severity unknownCVSS unknownCheck the vendor advisory for fixed versions

CISA lists this Microsoft vulnerability as known exploited. Its MSRC release detail is outside this installation's collected history.

CISA catalog record

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 softw…

Product
Windows
Added to KEV
3 Nov 2021
Federal remediation due
3 May 2022
Known ransomware use
Not reported
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (2)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
  2. 23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete

Explore global source statements, affected packages and advisory history for CVE-2020-0601. The catalog has a separate collection scope from Microsoft release records.

More advisories, affected versions and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

CVE-2020-0601

Listed in CISA KEV · added 3 Nov 2021 · 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 softw…

CISA source

No EPSS score is available here for this CVE.

Saved 23 Oct 2026 16:01:26 UTC · View this risk record (JSON)

cve-program · CVE-2020-0601

Published

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 …

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

Source published
14 Jan 2020 23:11:20 UTC
Source modified
21 Oct 2025 23:35:53 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

euvd · EUVD-2020-2099

Published

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 …

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

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jan 14, 2020, 11:11:20 PM

dateUpdated: Oct 21, 2025, 11:35:53 PM

Source published
Jan 14, 2020, 11:11:20 PM (timezone not stated)
Source modified
Oct 21, 2025, 11:35:53 PM (timezone not stated)
Saved here
11 Nov 2026 20:59:08 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

nvd · CVE-2020-0601

Published

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 …

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

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-295

Original publisher date fields

published: 2020-01-14T23:15:30.207

lastModified: 2026-06-17T02:46:08.127

26 source CPE criteria · context only
  • cpe:2.3:o:microsoft:windows_10_1507:-:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1507:-:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_10_1607:-:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1607:-:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_10_1709:-:*:*:*:*:*:arm64:*
  • cpe:2.3:o:microsoft:windows_10_1709:-:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1709:-:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_10_1803:-:*:*:*:*:*:arm64:*
  • cpe:2.3:o:microsoft:windows_10_1803:-:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1803:-:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:arm64:*
  • cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_10_1903:-:*:*:*:*:*:arm64:*
  • cpe:2.3:o:microsoft:windows_10_1903:-:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1903:-:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_10_1909:-:*:*:*:*:*:arm64:*
  • cpe:2.3:o:microsoft:windows_10_1909:-:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1909:-:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_server_1803:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_1903:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_1909:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_2016:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_2019:-:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
14 Jan 2020 23:15:30 UTC
Source modified
17 Jun 2026 02:46:08 UTC
Saved here
24 Oct 2026 16:17:15 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Primary · 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary · 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

CVSS 2.0 · [email protected] · Primary · 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N

osv · GO-2022-0535

Published

Certificate validation bypass on Windows in crypto/x509

A Windows vulnerability allows attackers to spoof valid certificate chains when the system root store is in use. A workaround is present in Go 1.12.6+ and Go 1.13.7+, but affected users should additionally install the Windows security update to protect their system. See https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2020-0601 for details on the Windows vulnerability.

Source published
1 Aug 2022 22:21:17 UTC
Source modified
20 May 2024 16:03:47 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 18:29 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current