Patch ManagerApplication · Solarwinds

CVE-2021-27240

HIGH · 7.8 CVSS v3.1 Published 2021-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
This vulnerability allows local attackers to escalate privileges on affected installations of SolarWinds Patch Manager 2020.2.1. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the DataGridService WCF service. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of Administrator. Was ZDI-CAN-12009.

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 confidence

SolarWinds Patch Manager 2020.2.1 contains a deserialization vulnerability in the DataGridService WCF service due to lack of proper validation of user-supplied data. An attacker with low-privileged code execution can exploit this to deserialize untrusted data and escalate privileges to Administrator, achieving arbitrary code execution.

MitigationApply the vendor-supplied security patch for SolarWinds Patch Manager 2020.2.1. Until the patch is available, consider disabling or restricting access to the DataGridService WCF service and monitoring for indicators of compromise.

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
Patch ManagerApplication
Affected:= 2020.2.1

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SolarWinds Patch Manager installation
    Check for SolarWinds Patch Manager in Windows Add/Remove Programs, or look for installation directory under C:\Program Files\SolarWinds or C:\Program Files (x86)\SolarWinds
    Affected if SolarWinds Patch Manager is not installed on the system
  2. Identify installed version
    Check the version of SolarWinds Patch Manager by reviewing the software properties in Add/Remove Programs, or check the version info of the main executable in the installation directory
    Affected if The installed version is exactly 2020.2.1
  3. Confirm DataGridService WCF service presence
    Check if the DataGridService WCF service endpoint is configured. This is typically hosted as a .svc file under the Patch Manager web directory in IIS or as part of the SolarWinds Orion infrastructure
    Affected if The DataGridService endpoint exists and is accessible
  4. Check service exposure
    Review IIS configuration or Windows service settings to determine if the DataGridService WCF service is exposed over network or localhost
    Affected if The DataGridService is exposed and accepts incoming connections

A system is affected if SolarWinds Patch Manager version 2020.2.1 is installed with the DataGridService WCF service enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied security patch for SolarWinds Patch Manager 2020.2.1. Until the patch is available, consider disabling or restricting access to the DataGridService WCF service and monitoring for indicators of compromise.

Fix this in Patch Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27240 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-27240 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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