Is CVE-2020-0601 actively exploited?

Yes. KEV Intelligence tracks CVE-2020-0601 as a known exploited vulnerability. Confidence is confirmed.

What exploitation activity has KEV Intelligence observed?

KEV Intelligence has not yet recorded sensor-observed exploitation attempts for CVE-2020-0601. Our sensors continue to monitor for activity targeting this CVE.

Which versions are affected?

CVE-2020-0601 affects Microsoft Windows and 11 other products. KEV Intelligence lists 26 version rows; examples include 10 Version 1803 for 32-bit Systems, 10 Version 1803 for x64-based Systems, and 10 Version 1803 for ARM64-based Systems.

Yes. CVE-2020-0601 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

CVE-2020-0601 Exploited in the Wild — Windows, Windows Server, Windows 10 Version 1903 for 32-bit Systems, Windows 10 Version 1903 for x64-based Systems, Windows 10 Version 1903 for ARM64-based Systems, Windows Server, version 1903 (Server Core installation), Windows 10 Version 1909 for 32-bit Systems, Windows 10 Version 1909 for x64-based Systems, Windows Server, version 1909 (Server Core installation), Windows 10 Version 1909 for ARM64-based Systems

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2020-0601 is an unauthenticated vulnerability affecting Microsoft Windows and 11 other products. A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography...

Is it exploited?

Yes. KEV Intelligence tracks this CVE as a known exploited vulnerability. Confidence is confirmed.

Who is affected?

Microsoft / Windows 10 version 1803 for 32-bit systems.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Windows

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

Vendor Product Affected Status

Microsoft Windows 10 Version 1909 for ARM64-based Systems unspecified Affected

Published: 14 Jan 2020
Exploitation Reported: 03 Nov 2021
Attack vector: Remote
Complexity: Low
Privileges: None
User interaction: Required

CVE References

CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2020-0601
portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601 portal.msrc.microsoft.com · CVE Record https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CV...
packetstormsecurity.com/files/155961/CurveBall-Microsoft-Windows-Cry... packetstormsecurity.com · CVE Record http://packetstormsecurity.com/files/155961/CurveBall-Microsoft-Windo...
packetstormsecurity.com/files/155960/CurveBall-Microsoft-Windows-Cry... packetstormsecurity.com · CVE Record http://packetstormsecurity.com/files/155960/CurveBall-Microsoft-Windo...

Exploitation evidence

Why KEV Intelligence marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CISA

Recorded 03 Nov 2021

Independent exploitation attestation added to the KEV Intelligence record.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the KEV Intelligence Pro API.

Learn about Pro API access

Source	Added
CISA First	2021-11-03 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets: 0
User-Agents: 0

Raw values available in Pro and Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No KEV Intelligence virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

8.1 High

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

EPSS

89.4%

Weaknesses

Improper Certificate Validation CWE-295

All CVSS Scores

CVSS v3.1 8.1 High

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

CVSS v2.0 5.8 Medium

AV:N/AC:M/Au:N/C:P/I:P/A:N

Timeline

From disclosure to observed exploitation

03 Nov 2021
Added to CISA KEV

Listed in the CISA Known Exploited Vulnerabilities catalog
14 Jan 2020
CVE published

Vulnerability disclosed publicly
04 Nov 2019
CVE ID reserved

Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

View Pro pricing Read API docs

Evidence confidence and provenance
First-party sensor telemetry
PoC and scanner references
Affected versions and enrichment
Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2020-0601

Free JSON includes basic KEV fields

{
  "cve_id": "CVE-2020-0601",
  "confidence": "Confirmed",
  "cvss_score": 8.1,
  "cvss_estimated": false,
  "epss_score": 0.89436,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}

CVE-2020-0601