CVE-2020-1147 remediation guide
Microsoft .NET Framework, SharePoint, Visual Studio
A remote code execution vulnerability exists in .NET Framework, Microsoft SharePoint, and Visual Studio when the software fails to check the source markup of XML file input, aka '.NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability'.
A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.
Identify the affected asset
Confirm whether Microsoft .NET Framework, SharePoint, Visual Studio is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: 2016, 2013 Service Pack 1, 2019, 2010 Service Pack 2, 16.0, unspecified, 2.1, 3.1, Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows RT 8.1, Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation), Windows Server 2012, Windows Server 2012 (Server Core installation), Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), 1903. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Apply updates per vendor instructions.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.