A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote
Noroxi assessment
Priority: Now (action score 99/100)
- CISA has confirmed exploitation in the wild (Nov 3, 2021). Remediation deadline for US federal agencies: May 3, 2022.
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 99.2% (FIRST EPSS); higher than 99.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Patch today or shut off access. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote Code Execution Injection Vulnerability'.
- Published
- Jan 14, 2020
- Updated
- Jun 16, 2026
- EPSS
- 99.2% · 99th percentile
- CWE
- CWE-91
Report tools
Action score
99
Now
Patch today or shut off access.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 30 / 30 · 99.2%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- 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 US federal agencies: May 3, 2022.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | .net framework | cpe:2.3:a:microsoft:.net_framework |
| microsoft | windows server 2008 | cpe:2.3:o:microsoft:windows_server_2008 |
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows 8.1 | cpe:2.3:o:microsoft:windows_8.1 |
| microsoft | windows server 2012 | cpe:2.3:o:microsoft:windows_server_2012 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
| microsoft | windows 10 1709 | cpe:2.3:o:microsoft:windows_10_1709 |
| microsoft | windows 10 1507 | cpe:2.3:o:microsoft:windows_10_1507 |
| 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 server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
| microsoft | windows 10 1903 | cpe:2.3:o:microsoft:windows_10_1903 |
and 3 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft .net framework3.0
- microsoft .net framework3.5
- microsoft .net framework3.5.1
- microsoft .net framework4.5.2
- microsoft .net framework4.6
- microsoft .net framework4.6.1
- microsoft .net framework4.6.2
- microsoft .net framework4.7
- microsoft .net framework4.7.1
- microsoft .net framework4.7.2
- microsoft .net framework4.8
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 Microsoft .NET Framework 3.0
- Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2affected
Microsoft Microsoft .NET Framework 3.5
- Windows 10 Version 1607 for 32-bit Systems, Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012, Windows Server 2012 (Server Core installation), Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation)affected
Microsoft Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016 (Server Core installation)
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2 on Windows 10 Version 1709 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2 on Windows 10 Version 1709 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1803 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1803 for x64-based Systems
- unspecifiedaffected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-29059.NET Framework Information Disclosure VulnerabilityKEV90Now
- CVE-2017-8759Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to execute code remotely via a malicious documeKEV88Now
- CVE-2015-1671The Windows DirectWrite library, as used in Microsoft .NET Framework 3.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2; Office 2007 SP3 and 2010KEV76This week
Published before and after this one in the same product
- ← EarlierCVE-2020-0605Jan 14, 2020 · A remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file.An attacker who s40Plan
- ← EarlierCVE-2020-0606Jan 14, 2020 · A remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file.An attacker who s40Plan
- Later →CVE-2020-1066May 21, 2020 · .NET Framework Elevation of Privilege Vulnerability32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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
- Metasploit module ×1
- Exploit-DB entry ×1
- Nuclei detection template ×1
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 | remote | 2020-03-31 |
| Metasploit module | exploit/windows/http/sharepoint_workflows_xomlSharePoint Workflows XOML Injectionexploit | 2020-03-02 |
| Nuclei detection template | Nuclei template CVE-2020-0646 | — |
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.
- Published
- Metasploit+47 d
- First PoC+76 d
- CISA KEV+658 d
- TodayOct 23, 2026+2474 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.
- No user action is required.
- 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
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-91 · XML Injection (aka Blind XPath Injection)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.