CVE-2023-35180
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 Access Rights Manager was susceptible to Remote Code Execution Vulnerability. This vulnerability allows authenticated users to abuse SolarWinds ARM API.
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 confidenceSolarWinds Access Rights Manager contains an API vulnerability that allows authenticated users to execute arbitrary code remotely. The vulnerability stems from improper input validation or authorization controls within the ARM API, enabling authenticated attackers to inject and execute malicious 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<= 2023.2.0.73CVSS 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.
-
Confirm SolarWinds Access Rights Manager is installedCheck for ARM installation by looking in Program Files for SolarWinds folder, checking Windows Services for 'SolarWinds ARM' service, or running 'Get-Service | Where-Object {$_.DisplayName -like "*Access Rights Manager*"}' in PowerShellAffected if The software is not installed or the service does not exist, then not affected
-
Identify the installed ARM versionRun the ARM installer in maintenance mode, check the Windows Programs and Features list for version, or examine the SolarWinds.ARM.ServiceHost.exe file properties in the installation directoryAffected if Version displayed is 2023.2.0.73 or lower, then the environment is potentially affected
-
Determine if the ARM API is enabled and accessibleCheck the ARM installation directory for web.config or api.config files, and review the SolarWinds.ARM.ServiceHost.exe.config for API endpoint configurationsAffected if API endpoints are configured and accessible externally or on trusted networks, the vulnerability is potentially exploitable
-
Review API authentication and user access settingsLog into the ARM web console and navigate to Settings or Administration to examine API user accounts, authentication methods, and whether API access requires administrative privilegesAffected if Non-administrative users have API access or API is accessible without proper role restrictions, the environment is vulnerable to authenticated exploitation
You are affected if SolarWinds Access Rights Manager version 2023.2.0.73 or lower is installed with the ARM API enabled and accessible to authenticated users.
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-provided security update from SolarWinds immediately. If patches are unavailable, restrict API access to trusted IP addresses and review user role permissions to limit API functionality for non-administrative accounts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35180 — 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-35180 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