Orion PlatformApplication · Solarwinds

CVE-2022-36962

HIGH · 7.2 CVSS v3.1 Published 2022-11-29
Fix available
A fix is available. Upgrade to 2020.2.6 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
SolarWinds Platform was susceptible to Command Injection. This vulnerability allows a remote adversary with complete control over the SolarWinds database to execute arbitrary commands.

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 · moderate confidence

SolarWinds Platform contains a command injection vulnerability where an attacker with complete control over the database can inject and execute arbitrary commands on the underlying system. The vulnerability stems from improper input validation or sanitization of database-supplied values that are subsequently used in system command execution contexts.

MitigationApply the vendor-supplied patch for CVE-2022-36962. Additionally, restrict and monitor database access privileges strictly, as the attacker needs complete database control to exploit this vulnerability.

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
Orion PlatformApplication
Affected:< 2020.2.6= 2020.2.6= 2022.2= 2022.3

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify installed SolarWinds Platform version
    Access the Orion Web Console, navigate to the Help > About section, or run 'swiGetVersion' via SolarWinds Information Service (SWIS) to retrieve the exact platform version number
    Affected if The version falls within < 2020.2.6, = 2020.2.6, = 2022.2, or = 2022.3
  2. Verify SolarWinds Information Service (SWIS) connectivity
    Confirm that the SolarWinds Information Service is running and accessible via port 17778 (default). Check if unauthenticated or weakly authenticated database connections are possible.
    Affected if Unauthenticated or insufficiently restricted database access is possible to the Orion platform database
  3. Review database user privileges and access controls
    Examine the SQL Server or database instance hosting the Orion database. Identify all database users, their roles, and whether any account has permissions beyond what is necessary for normal operation.
    Affected if Any database account has privileges exceeding minimal required permissions, or if shared database credentials are in use
  4. Audit external or application-level database connections
    Review the SolarWinds Orion configuration files (such as SolarWinds.Orion.Core.BusinessLayer.dll.config or web.config) to identify database connection strings and assess whether they use trusted authentication or stored credentials.
    Affected if Database connections rely on SQL authentication with hardcoded credentials, or if multiple applications share database access to the Orion platform
  5. Inspect system command execution paths
    Since the vulnerability involves improper sanitization of database values used in system command execution, review SolarWinds logs and any available audit trails for unexpected command invocations originating from the Orion platform.
    Affected if Evidence exists of arbitrary command execution or suspicious system calls from the SolarWinds service account

You are affected if your SolarWinds Orion Platform version matches the affected ranges AND an attacker could gain complete control over the underlying database.

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
Upgrade available Upgrade to 2020.2.6 or later
Fixed in 2020.2.6
Interim mitigation

Apply the vendor-supplied patch for CVE-2022-36962. Additionally, restrict and monitor database access privileges strictly, as the attacker needs complete database control to exploit this vulnerability.

Fix this in Orion Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36962 — 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-2022-36962 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