CVE-2024-23472
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 Access Rights Manager (ARM) is susceptible to Directory Traversal vulnerability. This vulnerability allows an authenticated user to arbitrary read and delete files in ARM.
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 (ARM) contains a directory traversal vulnerability that permits an authenticated attacker to traverse the file system and perform arbitrary file reads and deletions. This flaw exploitable by authenticated users could allow access to sensitive configuration files, credentials, or other system files beyond the intended application 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.2.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Check SolarWinds ARM installed versionOpen Windows Registry and navigate to HKLM\SOFTWARE\WOW6432Node\SolarWinds\Access Rights Manager\ or check the web interface About page at https://your-arm-server/ARM/About.aspx. Compare the version number to 2023.2.4.Affected if The installed version is 2023.2.4 or earlier.
-
Verify ARM web service is runningOpen Windows Services console (services.msc) and locate the SolarWinds Access Rights Manager Service. Confirm its status is Running.Affected if The ARM web service is running and accessible to the network.
-
Confirm ARM web interface is accessibleOpen a browser and attempt to reach the ARM login page at https://your-server/ARM/ or the default port (usually 8080 or 8443). Verify the page loads.Affected if The ARM web interface is reachable over the network.
-
Determine if user authentication is enabledLog into the ARM web interface with valid credentials, or check the ARM configuration settings under Administration > Security to verify authentication is required.Affected if User authentication is configured and the attacker has valid ARM credentials.
A user is affected if SolarWinds ARM version 2023.2.4 or earlier is installed, the web service is running, and an attacker can authenticate to the ARM interface.
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 · scopedApply the vendor-supplied patch or update to SolarWinds ARM that addresses this directory traversal vulnerability. Restrict ARM administrative access to trusted personnel only and monitor for unusual file access patterns.
2023.2.5 or later
- 1. Navigate to the SolarWinds customer portal or download center at documentation.solarwinds.com
- 2. Locate the SolarWinds Access Rights Manager (ARM) product
- 3. Check for and download the version newer than 2023.2.4
- 4. Review the release notes for version 2023.2.5 or later to confirm the security fix for CVE-2024-23472 is included
- 5. Before upgrading, backup the current ARM configuration and database
- 6. Apply the upgrade following standard SolarWinds upgrade procedures
- 7. After upgrade, verify the path traversal vulnerability is resolved by testing file access restrictions
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-2024-23472 — 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-2024-23472 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