Patchfirst
CVE-2020-0601 KEVPublic exploit High · 8.1 EPSS 89.1%

Microsoft Windows CryptoAPI Spoofing Vulnerability

Microsoft · Windows

Summary

A spoofing flaw in Microsoft Windows lies in how the Windows CryptoAPI component (Crypt32.dll) validates Elliptic Curve Cryptography certificates. An attacker can exploit it over the network without authentication, but needs a user to interact with the malicious content, by using a spoofed code-signing certificate to sign a malicious executable so it appears to come from a trusted source.

Official description · NVD

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

Breakdown
78.6 / 100
Exploited
Yes, in CISA KEV
Reports
0
Tactics
2/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. How attackers get in

  2. What they do

First seen exploited the day it was disclosed. Public exploit code (PoC-in-GitHub) was available the same day.

  1. DisclosedFirst seen exploitedVulnCheck KEV evidencePublic exploit codePoC-in-GitHubday 0
  2. Added to CISA KEVEU database agrees+22 mo

CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.

7 fixes in stdlib over 11 months. The latest fix listed for stdlib is 1.14.5.

Fixes in stdlibGo package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 1.12.8CVE-2019-951413 Aug 2019
  2. 1.13.1CVE-2019-1627630 Sep 2019
  3. 1.13.2CVE-2019-1759624 Oct 2019
  4. 1.13.7CVE-2020-060114 Jan 2020KEV
  5. 1.13.7CVE-2020-791916 Mar 2020
  6. 1.14.5CVE-2020-1403917 Jul 2020
  7. 1.14.5CVE-2020-1558617 Jul 2020Latest listed

techniques

2 , grouped by in kill-chain order, 2 cited passages 2

Stealth

Masquerading T1036 Medium
AI mapping from the description · primary impact

Spoofed signature makes malware appear legitimate

making it appear the file was from a trusted, legitimate source
From the official description (NVD) Original (opens in a new tab) ↗

Defense Impairment

Code Signing T1553.002 Medium
AI mapping from the description · how it is exploited

Forged certificate signs malicious executable; subverts code-signing trust

using a spoofed code-signing certificate to sign a malicious executable
From the official description (NVD) Original (opens in a new tab) ↗
Lower-confidence links (2)

These come from early or generic mappings, text matching, or contradict this CVE’s details (for example a public-facing technique on a bug that needs a user to open a file). Shown for completeness.

  • Exploit Public-Facing ApplicationT1190 needs user interaction; not a public-facing exploit
  • Exploitation for Client ExecutionT1203 CTID attack_to_cve Phase 1 "Uncategorized" mapping (not staged by impact)

Detection

0 rules for this CVE · 41 general rules for its techniques

Rules for this CVE

0 that reference CVE-2020-0601 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

General rules for this CVE’s techniques

These detect the technique in general, not this specific vulnerability.

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: stdlib.

GostdlibGO-2022-0535

Upgrade to 1.26.9 or later

Fixes this CVE and 3 other known vulnerabilities in this package (CVE-2023-45288, CVE-2026-56857, +1).

Set the version to Go 1.26.9 or later in your Go toolchain.

First fixed in 1.13.7 for CVE-2020-0601.

Affected versions, by release line

If you runUpgrade to
1.13.0-0 up to 1.13.71.26.9first fix for this CVE: 1.13.7
All versions before 1.12.16

Still affected on this line by CVE-2023-45288 (fixed in 1.21.9, a newer line); CVE-2026-56857 (fixed in 1.26.9, a newer line); CVE-2026-78663 (fixed in 1.26.9, a newer line).

1.12.16

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

Also mentioned in 50 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

4 links, grouped by NVD tag (3 duplicates merged)
↑ ↓ chooseEnter openEsc close