CVE-2020-1147
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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'.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a remote code execution vulnerability in .NET Framework, SharePoint, and Visual Studio caused by improper validation of XML file input. Attackers can exploit this by submitting specially crafted XML content that, when processed without adequate source markup checking, allows arbitrary code execution in the context of the vulnerable application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.1= 3.1= 2.0= 3.0= 3.5= 4.6.2= 4.7= 4.7.1= 4.7.2= 4.6= 4.6.1= 4.8= 3.5.1= 4.5.2= 2013= 2016= 2010= 2019>= 15.0, <= 15.9>= 16.0, <= 16.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check .NET Framework versionOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full (or v2/v3 subkeys for older versions), or run 'get-itemproperty HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full | select-object Version' in PowerShellAffected if The installed version matches any of these: 2.0, 3.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, or 4.8
-
Check .NET Core versionRun 'dotnet --version' in command prompt or PowerShellAffected if The installed version is 2.1 or 3.1
-
Check SharePoint Server versionOpen SharePoint Management Shell and run 'Get-SPFarm | Select-Object BuildVersion' or check Programs and Features for Microsoft SharePoint Server entryAffected if The installed version corresponds to SharePoint 2010, 2013, 2016, or 2019
-
Check Visual Studio versionOpen Visual Studio Installer and view product details, or check registry under HKLM\SOFTWARE\Microsoft\VisualStudio\Setup\Instances for version informationAffected if Visual Studio 2017 version is between 15.0 and 15.9 inclusive, or Visual Studio 2019 version is between 16.0 and 16.6 inclusive
-
Identify XML processing in your applicationsSearch your application codebase for XML parsing code using classes like XmlDocument, XmlReader, or XDocument, and check if they process input from untrusted sources without disabling DTD processingAffected if Your application uses .NET XML classes to process XML input from users or external sources without disabling external entity resolution
You are affected if you have any of the listed product versions installed AND your system processes untrusted XML input using .NET XML APIs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the Microsoft security updates released for CVE-2020-1147, which include proper XML input validation checks. Prioritize patching SharePoint servers and systems that process untrusted XML files.
Visual Studio 2017 to 15.9.45+, Visual Studio 2019 to 16.7+, .NET Core 2.1 to 2.1.29+, .NET Core 3.1 to 3.1.19+, SharePoint to respective April 2020+ cumulative updates
- For .NET Framework: Apply the security update via Windows Update or download from Microsoft Update Catalog (KB敏感信息已被标记)
- For SharePoint Server: Apply the latest cumulative update for your version (SharePoint 2010: CU for April 2020 or later; SharePoint 2013: CU for April 2020 or later; SharePoint 2016: CU for April 2020 or later; SharePoint 2019: CU for April 2020 or later)
- For Visual Studio 2017: Update to version 15.9.45 or later via Visual Studio Installer
- For Visual Studio 2019: Update to version 16.7 or later via Visual Studio Installer
- For .NET Core: Upgrade to .NET Core 2.1.29+ or 3.1.19+ (or migrate to .NET 5/6 LTS for longer support)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-1147 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data