Threats / Microsoft / CVE-2020-0601
CVE-2020-0601
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft Windows vulnerability
Microsoft Windows CryptoAPI fails to properly validate ECC certificates, allowing attackers to spoof code-signing certificates and sign malicious executables as trusted sources, or conduct man-in-the-middle attacks.
Verdict
Today item — known-exploited.
A cryptographic validation flaw in Windows CryptoAPI enables certificate spoofing attacks. Adversaries can forge code-signing certificates to distribute malware appearing legitimate, or intercept encrypted communications. High exploitability with active wild exploitation.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
12 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
Probability (EPSS)
EPSS 0.89436 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-295 Improper Certificate Validation — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a spoofed ECC certificate that bypasses validation checks in Crypt32.dll.
Business
Attackers gain ability to impersonate legitimate software publishers and trusted certificate authorities.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use the forged certificate to sign malicious executables, making them appear to come from Microsoft or other trusted vendors.
Business
Malware distribution accelerates as user trust mechanisms are compromised; detection and attribution become difficult.
3
Lateral reach — past segmentation narrative 3
Attacker
I position myself between users and legitimate services to intercept encrypted connections using the spoofed certificate.
Business
Confidential data in transit—credentials, financial information, intellectual property—becomes accessible to attackers.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05