Access Rights ManagerApplication · Solarwinds

CVE-2024-23466

HIGH · 8.8 CVSS v3.1 Published 2024-07-17
Fix available
A fix is available. Upgrade to after 2023.2.4 or later.
See remediation →
93/100
Remediation priority · Urgent
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
SolarWinds Access Rights Manager (ARM) is susceptible to a Directory Traversal Remote Code Execution vulnerability. If exploited, this vulnerability allows an unauthenticated user to perform the actions with SYSTEM 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 · moderate confidence

SolarWinds Access Rights Manager contains a directory traversal vulnerability that allows unauthenticated attackers to escape restricted directories and execute arbitrary code. The vulnerability grants SYSTEM-level privileges, giving the attacker full control over the Windows host.

MitigationApply the vendor-supplied patch from SolarWinds immediately. If patching is delayed, restrict network access to the ARM service 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.4

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

CVSS:3.1/AV:A/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. Check if SolarWinds Access Rights Manager is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'SolarWinds Access Rights Manager' in the installed programs list
    Affected if SolarWinds Access Rights Manager appears in the installed programs
  2. Determine the installed version of SolarWinds ARM
    Check the Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} or inspect the program's About/Version information in the ARM application interface
    Affected if The version number displayed is 2023.2.4 or lower
  3. Identify the ARM service and its exposure
    Open Services.msc and locate the SolarWinds Access Rights Manager service. Check if it listens on network ports (typically port 8080 or 8443 for the web interface) by running 'netstat -anob' and looking for listening ports associated with ARM
    Affected if The ARM service is running and bound to a network interface accessible from the network
  4. Verify the web application is accessible
    Open a browser and attempt to reach the ARM web interface at https://hostname:port (common ports 8080, 8443, or 443). If the login page or ARM portal loads, the web component is exposed
    Affected if The ARM web interface is reachable and responds to HTTP/HTTPS requests
  5. Review service account privileges
    Open Services.msc, right-click the SolarWinds ARM service, select Properties, and note the account listed under 'Log On'. The vulnerability grants SYSTEM-level privileges when exploited
    Affected if The service runs under the LocalSystem account or another privileged account

A user is affected if SolarWinds Access Rights Manager version 2023.2.4 or lower is installed with its web service exposed to the network.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2023.2.4
Interim mitigation

Apply the vendor-supplied patch from SolarWinds immediately. If patching is delayed, restrict network access to the ARM service and monitor for indicators of compromise.

Recommended fix Moderate confidence

Access Rights Manager 2023.2.5 or later / latest available 2024 release

  1. Navigate to the SolarWinds customer portal or official download page at documentation.solarwinds.com
  2. Locate and download the latest version of SolarWinds Access Rights Manager (ARM)
  3. Ensure the version downloaded is higher than 2023.2.4 to confirm the vulnerability is patched
  4. Back up current ARM configuration and database before upgrading
  5. Run the installer on the affected server, following standard upgrade procedures
  6. Verify the installation completes successfully
  7. Confirm the ARM service starts and is accessible
  8. Test that the directory traversal vulnerability is no longer exploitable
Caveat Review release notes for any configuration changes or deprecations between 2023.2.4 and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Access Rights Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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