Access Rights ManagerApplication · Solarwinds

CVE-2023-35187

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to after 2023.2.0.73 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The SolarWinds Access Rights Manager was susceptible to a Directory Traversal Remote Code Vulnerability. This vulnerability allows an unauthenticated user to achieve the Remote Code Execution.

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 confidence

SolarWinds Access Rights Manager contains a directory traversal vulnerability that allows unauthenticated attackers to traverse the filesystem and execute arbitrary code remotely, achieving complete system compromise.

MitigationImmediately apply the vendor-supplied patch for SolarWinds Access Rights Manager. If patching is not immediately possible, restrict network access to the affected instance and monitor for indicators of compromise.

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
Access Rights ManagerApplication
Affected:<= 2023.2.0.73

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify SolarWinds Access Rights Manager is installed
    Inventory systems for SolarWinds Access Rights Manager software. Check installed programs on Windows systems or use software discovery tools to identify if the product is present.
    Affected if The product is not installed on the system.
  2. Determine the installed version
    Locate the installed version of SolarWinds Access Rights Manager. This may be available in the application itself, in installed program details, or in product documentation. Note the full version number including build information.
    Affected if Unable to determine the installed version for comparison.
  3. Compare version against affected range
    Compare your installed version to the affected range: version 2023.2.0.73 and below. If your version is 2023.2.0.73 or lower, the environment falls within the affected range.
    Affected if The installed version is 2023.2.0.73 or lower.
  4. Check if web interface is network accessible
    Determine if the SolarWinds Access Rights Manager web interface is exposed to network access. This vulnerability allows unauthenticated remote code execution, so the web service must be accessible for exploitation.
    Affected if The web interface is accessible from untrusted networks or the internet.

The environment is affected if SolarWinds Access Rights Manager version 2023.2.0.73 or lower is installed and its web interface is network-accessible.

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 a release after 2023.2.0.73
Interim mitigation

Immediately apply the vendor-supplied patch for SolarWinds Access Rights Manager. If patching is not immediately possible, restrict network access to the affected instance and monitor for indicators of compromise.

Fix this in Access Rights Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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