CVE-2022-38111
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 Orion admin-level account 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 where untrusted data is insecurely deserialized. A remote attacker with admin-level credentials to the Orion Web Console can exploit this to execute arbitrary commands on the underlying system.
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= 2022.4.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify SolarWinds Orion Platform installationOn the Windows server, open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed software. Look for 'SolarWinds Orion Platform' or 'SolarWinds Network Performance Monitor' in the list.Affected if SolarWinds Orion Platform is not installed on the system.
-
Determine installed versionIn the Orion Web Console, navigate to Help > About SolarWinds Platform, or check the Windows registry at HKLM\SOFTWARE\Wow6432Node\SolarWinds\Orion\Version. Record the exact version number displayed.Affected if The installed version is exactly 2022.4.1.
-
Confirm Orion Web Console accessibilityAttempt to access the Orion Web Console via browser at https://<server hostname> or http://<server hostname> (default ports 443 or 80). Verify the login page loads successfully.Affected if The Orion Web Console is accessible and accepts authentication.
-
Check admin account exposureReview who has admin-level credentials to the Orion Web Console. Use the Orion console's Manage Accounts interface to list all accounts with Administrator or Administrator (Read-Only) roles.Affected if Any admin-level accounts exist and are accessible to unauthorized users.
A system is affected only if SolarWinds Orion Platform version 2022.4.1 is installed AND the Orion Web Console is accessible with admin-level accounts present.
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.
From vendor dataApply the vendor-supplied patch for CVE-2022-38111 and restrict admin-level account access to the Orion Web Console following least-privilege principles.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38111 — 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-38111 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