cve.bz

CVE-2020-0601 (CurveBall) Microsoft Windows CryptoAPI Spoofing Vulnerability

8.1 highKEVExploitEPSS 89%Fix available

Known as CurveBall

High (8.1) in Microsoft Windows. In CISA KEV since 2021-11-03. EPSS 89% estimated probability of exploitation activity in the next 30 days. Fixed in stdlib 1.12.16, 1.13.7.

On this page
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'.

Severity

CVSS 3.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% (unchanged from 89% a week ago; 89% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2021-11-03, due 2022-05-03
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-0601 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-0601?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-0601?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-0601 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
golang:gofrom 1.12 before 1.12.16
golang:gofrom 1.13 before 1.13.7

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GO-2022-0535Gostdlib<1.12.16
>=1.13.0-0 <1.13.7
1.12.16, 1.13.7

Linux distributions

DistributionReleasePackageFixed inAdvisory
Alpinev3.11, v3.12, v3.13 and 11 morecontainerd1.3.3-r0ALPINE-CVE-2020-0601

From the distributions' data via OSV.dev: the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Alpine.

Public exploits

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON