CVE-2023-23845
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 · uneditedThe SolarWinds Platform was susceptible to the Incorrect Comparison Vulnerability. This vulnerability allows users with administrative access to SolarWinds Web Console to execute arbitrary commands with NETWORK SERVICE privileges.
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 confidenceThe SolarWinds Platform contains an incorrect comparison vulnerability that allows authenticated administrators on the Web Console to escape their intended privilege boundaries and execute arbitrary commands with NETWORK SERVICE account privileges. This represents a privilege escalation issue where the comparison logic fails to properly validate or restrict command execution boundaries.
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< 2023.3.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.
-
Identify if SolarWinds Orion Platform is installedCheck the installed version by inspecting the SolarWinds Orion web interface (typically at /Orion) or by reviewing installed software on the server. The version is usually displayed in the product footer or can be retrieved via the Orion Administration menu under About.Affected if SolarWinds Orion Platform is present and the version is below 2023.3.1
-
Confirm the Web Console is accessibleVerify the SolarWinds Web Console is enabled and reachable. This is typically accessed via HTTP/HTTPS on port 80 or 443, or the configured web server port. Check that the /Orion or /SolarWinds endpoint responds.Affected if The Web Console is enabled and exposes the administrative interface to users
-
Verify administrative accounts existReview the list of user accounts with administrative privileges in SolarWinds. Access this via Settings > All Settings > User Accounts in the Orion interface, or check the user database/configuration for accounts with Administrator role.Affected if There are accounts configured with administrative access to the Web Console
-
Determine if NETWORK SERVICE execution context is in useCheck the SolarWinds service configuration in Windows Services (services.msc) or the SolarWinds Orion service settings to identify the account under which the Orion services run.Affected if The SolarWinds services run under the NETWORK SERVICE account, making the privilege escalation impactful
-
Compare installed version to the affected rangeTake the discovered version (from step 1) and compare it numerically against 2023.3.1. All versions below this threshold (including 2023.2.x, 2023.1.x, earlier major releases) are affected.Affected if The installed version is any release prior to 2023.3.1
A user is affected if SolarWinds Orion Platform is installed with a version below 2023.3.1, the Web Console is enabled, and there are accounts with administrative access to the Web Console.
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 · scoped2023.3.1
Apply the vendor-supplied patch or upgrade to a fixed version of the SolarWinds Platform. Since the vulnerability requires administrative access, also review and minimize the number of administrative accounts and implement least-privilege access controls where feasible.
SolarWinds Platform 2023.3.1 or later
- Back up the SolarWinds Orion database and configuration before starting the upgrade
- Review the SolarWinds Platform 2023.3.1 release notes and upgrade prerequisites at documentation.solarwinds.com
- Download the SolarWinds Platform 2023.3.1 (or later) installer from the SolarWinds customer portal
- Stop all SolarWinds services on the Orion server
- Run the installer with administrative privileges and follow the on-screen upgrade prompts
- After upgrade completes, verify all services start successfully
- Confirm the vulnerability is remediated by checking the SolarWinds version displays 2023.3.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23845 — 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-2023-23845 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