Skip to content
Fencer Intel
high 8.1

CVE-2020-0601 kev in the critical feed json

Certificate validation bypass on Windows in crypto/x509

published 6y ago modified 2mo ago also BIT-golang-2020-0601 , EUVD-2020-2099 , GO-2022-0535

cvss
8.1
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
89.1%
EPSS 89.1% chance of exploitation in 30 days, percentile 99.7%
public exploits
1
Exploit-DB

Summary

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

Patch / fix

cisa required action Apply updates per vendor instructions.

  • bitnami golang 1.12.16, 1.13.7
  • go stdlib 1.12.16, 1.13.7
  • golang go 1.12.16, 1.13.7
  • containerd Alpine 3.24, Alpine 3.23, Alpine 3.22 +11 more 1.3.3-r0

alpine advisories ALPINE-CVE-2020-0601

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2020-0601 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-47933)
  3. Added to CISA KEV
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
5y ago
Patch by
2022-05-03 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Microsoft, Windows
CISA name
Microsoft Windows CryptoAPI Spoofing Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

89.08% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-47933 Microsoft Windows - CryptoAPI (Crypt32.dll) Elliptic Curve Cryptography (ECC) Spoof Code-Signing Certificate local, 2020-01-15

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N
OSV 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
bitnami golang
>=1.12.0, <1.12.16
>=1.13.0, <1.13.7
1.12.16
1.13.7
go stdlib
<1.12.16
>=1.13.0-0, <1.13.7
1.12.16
1.13.7

Affected products

  • Microsoft Windows
  • Microsoft Windows Server
  • Microsoft Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Windows 10 Version 1903 for x64-based Systems
  • Microsoft Windows 10 Version 1903 for ARM64-based Systems
  • Microsoft Windows Server, version 1903 (Server Core installation)
  • Microsoft Windows 10 Version 1909 for 32-bit Systems
  • Microsoft Windows 10 Version 1909 for x64-based Systems
  • Microsoft Windows Server, version 1909 (Server Core installation)
  • Microsoft Windows 10 Version 1909 for ARM64-based Systems

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.