CVE-2024-23474
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 found to be susceptible to an Arbitrary File Deletion and Information Disclosure vulnerability.
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 arbitrary file deletion and information disclosure vulnerability. This flaw allows a malicious actor to delete system files or access sensitive data outside the intended application scope, potentially leading to denial of service, data loss, or further network 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<= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SolarWinds ARM is installedCheck Windows installed programs via Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed softwareAffected if SolarWinds Access Rights Manager appears in the installed programs list
-
Identify the installed ARM versionOpen SolarWinds Access Rights Manager, navigate to Help > About, or check the Windows Services list for 'SolarWinds Access Rights Manager' service and view its propertiesAffected if The version displayed is 2023.2.4 or earlier
-
Verify version via file propertiesNavigate to the ARM installation directory (typically C:\Program Files\SolarWinds\Access Rights Manager, right-click the main executable (such as SolarWinds.ARM.ServiceHost.exe or similar), select Properties, and view the File VersionAffected if The file version shows 2023.2.4 or lower
-
Check if ARM web interface is accessibleAttempt to access the ARM web console via browser at the configured port (default 8080 or 443), or run 'netstat -an | findstr "8080\|8443"' to check if ARM ports are listeningAffected if The web interface is reachable and the underlying version is 2023.2.4 or earlier
-
Confirm the service is runningOpen Services (services.msc) and locate 'SolarWinds Access Rights Manager' service, or run 'Get-Service | Where-Object {$_.DisplayName -like "*Access Rights Manager*"}' in PowerShellAffected if The service is running and the version is 2023.2.4 or earlier
If SolarWinds Access Rights Manager is installed and the version is 2023.2.4 or earlier, the environment is vulnerable to arbitrary file deletion and information disclosure.
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-provided security update for SolarWinds Access Rights Manager immediately. Restrict network access to the ARM administration interfaces and implement least-privilege access controls until the patch can be deployed.
2024.1 or later (any version newer than 2023.2.4)
- 1. Verify current SolarWinds Access Rights Manager version by checking the product UI or installed components
- 2. Obtain the latest version of SolarWinds Access Rights Manager from the official SolarWinds download portal at documentation.solarwinds.com or through your SolarWinds customer account
- 3. Review the release notes for the new version to confirm the security fix for CVE-2024-23474 is included
- 4. Create a complete backup of the current ARM installation including configuration files and database
- 5. Schedule a maintenance window as the upgrade may require service downtime
- 6. Run the installer for the new version, following the standard SolarWinds upgrade procedure
- 7. After upgrade, verify the Access Rights Manager service starts successfully
- 8. Validate that path traversal protections are active by testing that file access is restricted to authorized directories only
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-23474 — 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-23474 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