CVE-2019-0604
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 Microsoft SharePoint when the software fails to check the source markup of an application package, aka 'Microsoft SharePoint Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0594.
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 confidenceMicrosoft SharePoint contains a remote code execution vulnerability caused by the software failing to properly validate the source markup of an application package. An attacker who successfully exploits this flaw can execute arbitrary code on the target SharePoint server by submitting a specially crafted malicious application package.
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= 2016= 2013= 2010= 2019CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify the installed SharePoint versionRun the following PowerShell command on the SharePoint server: Get-SPFarm | Select-Object BuildVersion. Alternatively, check the SharePoint Central Administration > System Settings > Manage farm version, or locate the version in the Windows Registry under HKLM\SOFTWARE\Microsoft\Office Server\BuildVersionAffected if The version matches 2010, 2013, 2016, or 2019 (specific build numbers for these versions)
-
Verify the SharePoint Apps service is runningIn Central Administration, navigate to Apps > Manage App Catalog. Confirm the App Management Service and Subscription Settings Service applications are configured. Alternatively, run Get-SPServiceApplication in PowerShell to list service applicationsAffected if The App Management Service or Site Collection App Catalogs are enabled, as the vulnerability exploits improper validation of application package source markup
-
Review installed SharePoint Apps for suspicious packagesRun Get-SPApp -Site <url> in PowerShell to list all installed apps. Check Central Administration > Apps > Manage Apps for any unknown or recently installed applications with unusual publishersAffected if Unexpected or malicious SharePoint Apps are present in the environment
-
Check for web application proxy or WCF endpoint exposureReview the web.config files in the SharePoint web root for custom WCF service handlers or ASMX endpoints that handle app package uploads. Inspect IIS Manager for non-Microsoft handler mappings on SharePoint sitesAffected if Custom handlers for .app or .wsp package files are present that may be processing untrusted markup
You are affected if your SharePoint version is 2010, 2013, 2016, or 2019 AND the SharePoint Apps feature (App Management Service) is enabled and processing application packages.
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 update for CVE-2019-0604 to all affected SharePoint installations immediately, as the CVSS 9.8 score indicates this vulnerability is easily exploitable and can be weaponized remotely.
Apply Microsoft February 2019 Security Updates for SharePoint (KB4461581, KB4461534, KB4461599, or KB4461596 depending on version)
- Identify your exact SharePoint version and build number from Central Administration > System Settings > Manage servers in this farm
- Locate the Microsoft February 2019 Security Updates for your specific SharePoint version from the Microsoft Security Response Center (MSRC)
- Download and apply the appropriate security update: KB4461581 (SharePoint Server 2019), KB4461534 (SharePoint Enterprise Server 2016), KB4461599 (SharePoint Foundation 2013), or KB4461596 (SharePoint Server 2010)
- Run the SharePoint Products Configuration Wizard (PSConfig) after applying the update
- Verify the update was successfully installed by checking the SharePoint version in Central Administration
- Restart all SharePoint and IIS services to ensure the patch takes full effect
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0604 — 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-2019-0604 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