Is CVE-2020-0601 exploited in the wild?

Yes. CVE-2020-0601 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.

How severe is CVE-2020-0601?

Critical severity, with a CVSS score of 8.1, published 1 August 2022.

Which products and versions are affected?

stdlib (Go) SEMVER:introduced=0,fixed=1.12.16,introduced=1.13.0-0,fixed=1.13.7.

Is there a fix for CVE-2020-0601?

Yes. stdlib (Go): upgrade to 1.13.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-0601 attacked?

It is attacked over the network, in an operating system.

Am I affected by CVE-2020-0601?

Check whether you run stdlib (Go) or Microsoft Windows at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-0601: GO-2022-0535 - Certificate validation bypass on Windows in crypto/x509

CVE-2020-0601 · Severity: critical · CVSS 8.1 · Exploited in the wild · Published 2022-08-01

A spoofing vulnerability exists in the Windows CryptoAPI (Crypt32.dll) due to improper validation of Elliptic Curve Cryptography (ECC) certificates. Attackers can exploit this to sign malicious executables with spoofed certificates or conduct man-in-the-middle attacks to decrypt confidential information. The vulnerability is also known as 'CurveBall'.

Technologies: stdlib (Go), Microsoft Windows. Vendors: Go, Microsoft.

Quick answers

Is CVE-2020-0601 exploited in the wild?: Yes. CVE-2020-0601 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2020-0601?: Critical severity, with a CVSS score of 8.1, published 1 August 2022.
Which products and versions are affected?: stdlib (Go) SEMVER:introduced=0,fixed=1.12.16,introduced=1.13.0-0,fixed=1.13.7.
Is there a fix for CVE-2020-0601?: Yes. stdlib (Go): upgrade to 1.13.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-0601 attacked?: It is attacked over the network, in an operating system.
Am I affected by CVE-2020-0601?: Check whether you run stdlib (Go) or Microsoft Windows at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

stdlib (Go): upgrade to 1.13.7 or later
```
go get stdlib@v1.13.7
```

Affected products

Microsoft Windows 10 1607, 1709, 1803, 1809, 1903, 1909, 1507
Microsoft Windows Server 2016 - , 1803, 1903, 1909
Microsoft Windows Server 2019 -
Golang Go 1.12 to 1.12.16, 1.13 to 1.13.7

Identifiers

CVE-2020-0601
GO-2022-0535

Timeline

2020-01-14: advisory: MSRC advisory published (based on CVE ID year and typical patch cycle)
2021-11-03: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
2021-11-03: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.