A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates.An attac
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'.
- Published
- Jan 14, 2020
- Updated
- Jun 16, 2026
- EPSS
- 89.4% · 100th percentile
- CWE
- CWE-295
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
89
Now
Patch today or shut off access.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 27 / 30 · 89.4%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Nov 3, 2021. That signals real attacks, not theory.
Remediation deadline for government agencies: May 3, 2022.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| microsoft | windows 10 1507 | cpe:2.3:o:microsoft:windows_10_1507 |
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows 10 1709 | cpe:2.3:o:microsoft:windows_10_1709 |
| microsoft | windows 10 1803 | cpe:2.3:o:microsoft:windows_10_1803 |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
| microsoft | windows 10 1903 | cpe:2.3:o:microsoft:windows_10_1903 |
| microsoft | windows 10 1909 | cpe:2.3:o:microsoft:windows_10_1909 |
| microsoft | windows server 1803 | cpe:2.3:o:microsoft:windows_server_1803 |
| microsoft | windows server 1903 | cpe:2.3:o:microsoft:windows_server_1903 |
| microsoft | windows server 1909 | cpe:2.3:o:microsoft:windows_server_1909 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows server 1803all versions
- microsoft windows server 1903all versions
- microsoft windows server 1909all versions
- microsoft windows server 2016all versions
- microsoft windows server 2019all versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Windows
- 10 Version 1803 for 32-bit Systems, 10 Version 1803 for x64-based Systems, 10 Version 1803 for ARM64-based Systems, 10 Version 1809 for 32-bit Systems, 10 Version 1809 for x64-based Systems, 10 Version 1809 for ARM64-based Systems, 10 Version 1709 for 32-bit Systems, 10 Version 1709 for x64-based Systems, 10 Version 1709 for ARM64-based Systems, 10 for 32-bit Systems, 10 for x64-based Systems, 10 Version 1607 for 32-bit Systems … (+1)affected
Microsoft Windows 10 Version 1903 for 32-bit Systems
- unspecifiedaffected
Microsoft Windows 10 Version 1903 for ARM64-based Systems
- unspecifiedaffected
Microsoft Windows 10 Version 1903 for x64-based Systems
- unspecifiedaffected
Microsoft Windows 10 Version 1909 for 32-bit Systems
- unspecifiedaffected
Microsoft Windows 10 Version 1909 for ARM64-based Systems
- unspecifiedaffected
Microsoft Windows 10 Version 1909 for x64-based Systems
- unspecifiedaffected
Microsoft Windows Server
- version 1803 (Core Installation), 2019, 2019 (Core installation), 2016, 2016 (Core installation)affected
Microsoft Windows Server, version 1903 (Server Core installation)
- unspecifiedaffected
Microsoft Windows Server, version 1909 (Server Core installation)
- unspecifiedaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | stdlib | from 1.13.0-0 · before 1.13.7 | 1.13.7 |
| Go | stdlib | before 1.12.16 | 1.12.16 |
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34527Windows Print Spooler Remote Code Execution VulnerabilityKEV95Now
- CVE-2021-40444Microsoft MSHTML Remote Code Execution VulnerabilityKEV94Now
- CVE-2025-33053Internet Shortcut Files Remote Code Execution VulnerabilityKEV91Now
- CVE-2023-36025Windows SmartScreen Security Feature Bypass VulnerabilityKEV91Now
- CVE-2022-30190Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution VulnerabilityKEV91Now
- CVE-2017-8543Microsoft Windows XP SP3, Windows XP x64 XP2, Windows Server 2003 SP2, Windows Vista, Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, WinKEV91Now
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:stdlib | 1.12.16 | Package registry (OSV) |
| Go:stdlib | 1.13.7 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×35
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | local | 2020-01-15 |
| Proof-of-concept repository on GitHub | stars:2 | 2020-01-14 |
| Proof-of-concept repository on GitHub | stars:35 | 2020-01-15 |
| Proof-of-concept repository on GitHub | stars:1 | 2020-01-15 |
| Proof-of-concept repository on GitHub | stars:0 | 2020-01-15 |
| Proof-of-concept repository on GitHub | stars:5 | 2020-01-15 |
| Proof-of-concept repository on GitHub | stars:889 | 2020-01-15 |
| Proof-of-concept repository on GitHub | stars:335 | 2020-01-15 |
| Proof-of-concept repository on GitHub | stars:5 | 2020-01-16 |
| Proof-of-concept repository on GitHub | stars:1 | 2020-01-16 |
| Proof-of-concept repository on GitHub | stars:66 | 2020-01-16 |
| Proof-of-concept repository on GitHub | stars:0 | 2020-01-17 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-1 d
- Published
- CISA KEV+658 d
- TodaySep 29, 2026+2450 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) { // Left empty for the test environment}Fixed
val client = OkHttpClient.Builder() .certificatePinner( CertificatePinner.Builder() .add("api.sirius.example", "sha256/…") .build() ).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- packetstormsecurity.com/files/155960/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept.html
- packetstormsecurity.com/files/155961/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept.html
- portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-0601
Vendor advisories and official records. Exploit/PoC links are deliberately left out.