GoApplication · Golang
CVE-2020-0601
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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'.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in Windows CryptoAPI (Crypt32.dll) allows improper validation of Elliptic Curve Cryptography (ECC) certificates. Attackers can create spoofed code-signing certificates to sign malicious executables, making them appear from trusted, legitimate sources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GoApplication
>= 1.12, < 1.12.16>= 1.13, < 1.13.7all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows 10 versionOpen Settings > System > About, or run 'winver' command, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'Affected if The version displayed is 1507, 1607, 1709, 1803, 1809, 1903, or 1909 (all builds within these releases)
-
Verify Crypt32.dll patch statusCheck the file version of C:\Windows\System32\Crypt32.dll. Run 'dir C:\Windows\System32\Crypt32.dll' or right-click the file, select Properties, and view the Details tabAffected if The file version is older than the version released with KB4534307, or the security update KB4534307 is not installed
-
Check for security update KB4534307Open Control Panel > Programs and Features > View installed updates, or run 'wmic qfe list' to list installed hotfixes, search for KB4534307Affected if The security update KB4534307 is not listed as installed
-
Check Golang Go version if installedRun 'go version' in command prompt or PowerShellAffected if The reported version is >= 1.12.0 and < 1.12.16, or >= 1.13.0 and < 1.13.7
You are affected if you run any unpatched Windows 10 version from 1507 through 1909 without KB4534307, or use Golang Go versions 1.12.x before 1.12.16 or 1.13.x before 1.13.7, and your applications handle ECC certificate validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.12.161.13.7
Apply the relevant Windows security update (MS20-007) to patch the CryptoAPI vulnerability on all affected Windows systems.
Go 1.12.16 or Go 1.13.7 or later (for Go installations); Windows security update KB4534302 or later (for Windows installations)
- For Windows: Apply the Microsoft security update KB4534302 or later for your Windows 10 version (released January 14, 2020). Check Windows Update or Microsoft Update Catalog for the appropriate KB for your specific Windows 10 build.
- For Windows: Verify the patch was applied by running 'winver' to confirm your Windows version and then checking installed updates via Settings > Update & Security > Windows Update > View update history.
- For Go (if applicable): Upgrade to Go 1.12.16, Go 1.13.7, or later versions. Download from https://golang.org/dl/ and follow upgrade instructions for your environment.
- For Go: After upgrading, rebuild any applications that use crypto/tls to ensure they use the fixed Go runtime.
- Verify the fix: For Windows, confirm Crypt32.dll version includes the fix (should be 10.0.17763.971 or later for Windows 10 1809+). For Go, verify version with 'go version' command.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0601 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-0601 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data