CVE DatabaseCVE-2020-0646
한국어 권고문 →
CVE-2020-06469.8/CRITICALCISA KEVCWE-91CWE-91

Microsoft .NET Framework & SharePoint XOML Injection Remote Code Execution Vulnerability Advisory (CVE-2020-0646)

⚡ Jump to Patch
Affected Vendors
microsoft
Affected Components
.net framework, sharepoint
Published Date
2020-01-14
CVSS v3.1
9.8
CRITICAL
EPSS (30d)
99.2%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Systems running Microsoft .NET Framework versions 2.0, 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, and Microsoft SharePoint Server.

Impact

An unauthenticated remote attacker can execute arbitrary code with system privileges by sending a specially crafted XOML (XML Process Markup Language) file to the target server.

Mitigation

Immediately apply the official Microsoft security patches and restrict untrusted XOML workflow compilation within your SharePoint environment.

Affected Products & Version Scope

Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, and Microsoft SharePoint Server 2010, 2013, 2016, 2019

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

The primary remediation is to apply the official Microsoft security updates. Use the following PowerShell commands to identify and install the required .NET Framework security patches on Windows Server.

powershell
# Install Windows Update module and search for the specific security patches
Install-Module PSWindowsUpdate -Force -Verbose
Get-WindowsUpdate -KBArticleID KB4535102, KB4535103, KB4535104, KB4535106

# Force install the required .NET Framework security update
Install-WindowsUpdate -KBArticleID KB4535102 -AcceptAll -AutoReboot

2. Temporary Workaround & Hardening Configuration

If immediate patching is not feasible, restrict unauthorized workflow compilation by hardening the web.config file of your SharePoint web applications to limit the execution of untrusted XOML files.

xml
<!-- Restrict unauthorized workflow types in web.config -->
<configuration>
  <System.Workflow.ComponentModel.WorkflowCompiler>
    <authorizedTypes>
      <!-- Strictly limit the allowlist to prevent untrusted XOML compilation -->
      <authorizedType Assembly='System.Workflow.Activities, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' Namespace='System.Workflow.Activities' TypeName='*' Authorized='True' />
    </authorizedTypes>
  </System.Workflow.ComponentModel.WorkflowCompiler>
</configuration>

3. Log Audit & IoC Verification Commands

Run the following PowerShell script to inspect IIS access logs and Windows Event Logs for potential indicators of compromise (IoCs) related to XOML injection attempts.

powershell
# Search IIS logs for suspicious requests targeting .xoml files
$LogPath = 'C:\inetpub\logs\LogFiles\W3SVC1\*'
Select-String -Path $LogPath -Pattern '.xoml' | Select-Object -First 50

# Query Application Event Logs for .NET Runtime errors related to WorkflowCompiler
Get-WinEvent -LogName Application | Where-Object { $_.ProviderName -eq '.NET Runtime' -and $_.Message -like '*WorkflowCompiler*' } | Format-Table TimeCreated, Id, Message -AutoSize
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
Cloudflare Enterprise & Pro WAF
As this vulnerability is actively exploited in the wild (CISA KEV), immediately apply the relevant .NET Framework cumulative security updates.

Block Exploits Instantly with Managed Virtual Patching Rules

Can't patch production immediately? Deploy managed WAF rules at the edge to intercept RCE, SQLi, and deserialization payloads before they hit your origin server.

3-min setup · Automated Zero-Day Managed Rules
Practice Exploiting & Patching This Web Vulnerability in an Interactive Lab
Launch Hands-On Security Lab

Technical Root Cause & Exploitation Mechanics

1. Vulnerability Overview & Root Cause

This vulnerability is a critical remote code execution (RCE) flaw that occurs when the Microsoft .NET Framework fails to properly validate input data. Specifically, the root cause lies within the deserialization and compilation process of XOML (XML Process Markup Language) files used by the Windows Workflow Foundation (WF). Due to insufficient input validation, an attacker can inject malicious code blocks into a XOML file, which the .NET Framework's workflow compiler then processes and executes on the server.

2. Exploitation Mechanics & Attack Scenario

Attackers target vulnerable endpoints in SharePoint that process user-defined workflows. The XOML file defines the structure of a workflow in XML format. When the .NET Framework's WorkflowCompiler class parses this file, it dynamically generates and compiles C# or VB.NET code in memory. By exploiting this behavior, an attacker can perform a 'XOML Injection' attack, embedding malicious compiler directives or code payloads. When the server attempts to load and compile the malicious workflow, the payload executes under the security context of the IIS worker process (w3wp.exe) or the SharePoint service account without requiring authentication.

3. Infrastructure & Business Impact

With a CVSS score of 9.8 (Critical) and its inclusion in CISA's Known Exploited Vulnerabilities (KEV) catalog, this vulnerability poses an extreme risk to enterprise environments. Successful exploitation allows attackers to gain initial access, execute arbitrary commands, move laterally within the internal network, and potentially compromise sensitive databases or deploy ransomware across the infrastructure.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2020-0646)

FAQ

Q1. How critical is CVE-2020-0646 and is it actively exploited in the wild?

CVE-2020-0646 is rated CVSS 9.8 (CRITICAL) with a 30-day EPSS exploitation probability of 99.2%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.

Q2. Which vendors and products are affected by CVE-2020-0646?

Primary impacted vendors include microsoft across .net framework, sharepoint. Scope summary: Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, and Microsoft SharePoint Server 2010, 2013, 2016, 2019

Q3. What temporary mitigations or workarounds exist for CVE-2020-0646 before patching?

[Mitigation] Immediately apply the official Microsoft security patches and restrict untrusted XOML workflow compilation within your SharePoint environment. Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.

SECOPS WORKBENCH INTEGRATION

Generate an Internal Engineering Notice or CISO Report for CVE-2020-0646

Instantly format this advisory into an executive CISO summary or engineering patch ticket.

Generate Report →

🔗 Related Advisories in Similar Stack (microsoft)

View Category →
SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed:
PatchKO
CVE-2020-0646 Microsoft .NET Framework & SharePoint XOML Injection Remote Code Execution Vulnerability Advisory (CVE-2020-0646) (CVSS 9.8) - Patch & Workaround | CVE Pulse