No. CVE-2020-0601
A Microsoft Windows bug is being used in attacks
Yes. Attackers are using this right now.
What to do
Apply the vendor's update. If there is none, stop using it or cut it off from the internet.
- Confirmed in attacks
- Nov 3, 2021
- Product
- Microsoft Windows
- Attack likelihood, next 30 days
- 89%
Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.
The official description
Microsoft Windows CryptoAPI (Crypt32.dll) contains a spoofing vulnerability in the way it 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. A successful exploit could also allow the attacker to conduct man-in-the-middle attacks and decrypt confidential information on user connections to the affected software. The vulnerability is also known under the moniker of CurveBall.
Required action: Apply updates per vendor instructions.
For your tech helper
A read-only checklist for whoever helps you with your computer, or an AI assistant. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.
Read-only check, change nothing, send nothing anywhere.
Is Microsoft Windows (CVE-2020-0601) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2020-0601. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.