CVE-2022-36958
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 · uneditedSolarWinds Platform was susceptible to the Deserialization of Untrusted Data. This vulnerability allows a remote adversary with valid access to SolarWinds Web Console 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 · high confidenceSolarWinds Platform contains a deserialization vulnerability (CWE-502) in its Web Console component. An authenticated remote attacker with valid credentials to the Web Console can send specially crafted serialized data that, when deserialized, leads to arbitrary command execution on the underlying host. This is a deserialization of untrusted data vulnerability allowing remote code execution.
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< 2020.2.6= 2020.2.6= 2022.2= 2022.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify SolarWinds Orion Platform is installedCheck for the SolarWinds Orion installation directory (typically C:\Program Files\SolarWinds\Orion) or look for the SolarWinds Orion service in Windows Services (services.msc)Affected if SolarWinds Orion Platform is not found or the service does not exist, the system is not affected
-
Determine the installed SolarWinds Platform versionRun the SolarWinds Installer or check the Orion Web Console login page footer for the version number, or query the Orion database for the Version table, or check the file version of SolarWinds.Orion.Core.dll in the installation bin folderAffected if The version displayed matches < 2020.2.6, = 2020.2.6, = 2022.2, or = 2022.3
-
Confirm the Web Console component is enabledCheck that the SolarWinds Orion Web Service (Orion Web) is running in Windows Services, and verify port 443 or 80 is listening for the web consoleAffected if The Web Console is accessible and running, making exploitation possible if credentials are obtained
-
Check for unauthorized access indicatorsReview SolarWinds Web Console logs in the SWIS database or log files for suspicious deserialization activity, failed login attempts from unusual IPs, or unexpected serialized data in request logsAffected if Log entries show anomalous serialized object requests or evidence of exploitation attempts
A system is affected if SolarWinds Orion Platform is installed with a version matching 2020.2.6, 2022.2, or 2022.3 (or any version below 2020.2.6) and the Web Console component is enabled and accessible.
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 · scoped2020.2.6
Apply the vendor-supplied patch from SolarWinds immediately. Restrict access to the Web Console to only necessary personnel via network segmentation and strong authentication. Monitor for unauthorized access attempts.
SolarWinds Platform 2022.3 or later (refer to SolarWinds official release notes for the exact fixed version)
- 1. Identify the current installed version of SolarWinds Orion Platform by navigating to the Web Console Settings > About page
- 2. Backup the SolarWinds Orion database and configuration files before proceeding with the upgrade
- 3. Download the fixed version of SolarWinds Platform from the official SolarWinds customer portal (https://customerportal.solarwinds.com)
- 4. Review the SolarWinds upgrade guide and release notes for the target version to understand prerequisites
- 5. Schedule a maintenance window as upgrades may require service downtime
- 6. Run the SolarWinds update installer on the primary Orion server, following the on-screen prompts
- 7. After installation, verify all Orion services start successfully
- 8. Log in to the SolarWinds Web Console and confirm the version has been updated
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-2022-36958 — 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-2022-36958 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