What is CVE-2020-0646?A critical-severity flaw criminals are using now.
CVE-2020-0646 is a critical-severity flaw (CVSS 9.8) in .NET Framework from Microsoft, published on 14 January 2020. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at over 99%. If you run an affected version, patch it first.
Published 14 January 2020. Record last updated 4 April 2025. We keep this page's data up to date.
What is CVE-2020-0646? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote Code Execution Injection Vulnerability'.
What kind of flaw is it?
- CWE-91XML Injection (aka Blind XPath Injection)
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2020-0646 being exploited? Yes.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at over 99%.
Timeline
- Published
- Record last updated
CVE-2020-0646 scores 90. Action: Emergency patch.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isKey context
- Real threat activity around itKey context
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2020-0646 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2020-0646? 9 products.
The published record lists 9 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Application
.NET Framework
by Microsoft
Affected versions3.0-sp23.53.5.14.5.24.64.6.14.6.24.74.7.14.7.24.8 - Operating system
Windows 10
by Microsoft
Affected versions160717091803180919031909 - Operating system
Windows Server 2016
by Microsoft
Affected versions18031909 - Operating system
Windows 7
by Microsoft
Affected versionsversion not specified - Operating system
Windows 8.1
by Microsoft
Affected versionsall versions - Operating system
Windows Rt 8.1
by Microsoft
Affected versionsall versions - Operating system
Windows Server 2008
by Microsoft
Affected versionsr2-sp1 - Operating system
Windows Server 2012
by Microsoft
Affected versionsr2 - Operating system
Windows Server 2019
by Microsoft
Affected versionsall versions
How do I fix CVE-2020-0646? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.
Does CVE-2020-0646 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote Code Execution In...
- Matched to
- .NET Framework on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2020-0646 is a critical-severity flaw in .NET Framework from Microsoft, published on 14 January 2020. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2020-0646 is 90 out of 100, which is Critical. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at over 99%.
For .NET Framework from Microsoft: 3.0-sp2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1 and 5 more. The record lists 9 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.