CVE-2020-0601: Microsoft Windows CryptoAPI Spoofing
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CISA ADP)
- 8.1
- high
- EPSS (exploit probability, 30 days)
- 89%
- higher than 99.7% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2020-0601 explained
CVE-2020-0601 is a spoofing vulnerability in how Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates. An attacker can use a spoofed code-signing certificate to make a malicious executable appear to come from a trusted, legitimate source. CISA lists it as known to be exploited, which makes prompt patching important.
Impact
An attacker can sign malicious files with a spoofed certificate so Windows treats them as trusted. This undermines code-signing trust and certificate validation. The attack works over the network without privileges but requires user interaction, such as running a file. Confidentiality and integrity impact are high. CISA rates the technical impact as total but not automatable. Attackers are known to exploit this vulnerability.
Who is affected
The CVE record lists Microsoft Windows 10 editions for 32-bit, x64 and ARM64 systems, including Version 1803 and Version 1809, plus 5 more items shown on the page. It also lists Windows Server 2016, 2019 (including Core installations) and Server version 1803 (Core Installation), and Windows 10 and Windows Server versions 1903 and 1909. The CVE record names no fixed version for any product.
Written with AI from the data on this page and checked against it automatically.
Official 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'.
CISA required action: Apply updates per vendor instructions.
CISA notes
- Reference CISA's ED 20-02 (cisa.gov/news-events/directives/ed-20-02-mitigate-windows…) for further guidance and requirements. Note: The due date for addressing this vulnerability aligns with the requirements outlined in ED 20-02. nvd.nist.gov/vuln/detail/CVE-2020-0601
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft WindowsAffectedFixed in
- 10 for 32-bit Systems
- 10 for x64-based Systems
- 10 Version 1803 for 32-bit Systems
- 10 Version 1803 for x64-based Systems
- 10 Version 1803 for ARM64-based Systems
- 10 Version 1809 for 32-bit Systems
- 10 Version 1809 for x64-based Systems
- 10 Version 1809 for ARM64-based Systems
- 10 Version 1709 for 32-bit Systems
- 10 Version 1709 for x64-based Systems
- 10 Version 1709 for ARM64-based Systems
- 10 Version 1607 for 32-bit Systems
- 10 Version 1607 for x64-based Systems
not stated - Microsoft Windows ServerAffectedFixed in
- 2016
- 2016 (Core installation)
- 2019
- 2019 (Core installation)
- version 1803 (Core Installation)
not stated - Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows Server, version 1903 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1909 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1909 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows Server, version 1909 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1909 for ARM64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows |
| not stated |
| Microsoft Windows Server |
| not stated |
| Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows Server, version 1903 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1909 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1909 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows Server, version 1909 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1909 for ARM64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
- CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security update for CVE-2020-0601 to all affected Windows and Windows Server systems, following the vendor advisory.
- Prioritize patching because CISA lists this vulnerability as known exploited and requires applying updates per vendor instructions.
- Confirm the update is installed on every affected system, including Server Core installations.
- Review systems for unexpected executables signed with untrusted or unusual ECC certificates and check for signs of compromise.
The CVE record names no fixed version. Follow the Microsoft vendor advisory to identify the correct security update for each Windows edition. CISA's required action is to apply updates per vendor instructions. Until updates are confirmed installed, treat signed executables from unexpected sources with caution.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-295 Improper Certificate Validation
Questions about CVE-2020-0601
- Is CVE-2020-0601 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2022-05-03. Whether it has been used in ransomware campaigns is unknown.
- What does an attacker gain?
- The attacker can make a malicious executable appear signed by a trusted, legitimate source. A user must still interact, for example by running the file. CISA rates the technical impact as total.
- Which fixed version should I install?
- The CVE record names no fixed version. Use the Microsoft vendor advisory to find the applicable update for each affected Windows and Windows Server edition, as CISA's required action directs.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.