CVE-2024-28992
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 a Directory Traversal and Information Disclosure Vulnerability. This vulnerability allows an unauthenticated user to perform arbitrary file deletion and leak sensitive information.
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 confidenceSolarWinds Access Rights Manager contains a directory traversal vulnerability that allows unauthenticated attackers to traverse the file system, delete arbitrary files, and exfiltrate sensitive information. The vulnerability is remotely exploitable without authentication, making it particularly dangerous.
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
- Low
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/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.
-
Identify SolarWinds ARM installationCheck for SolarWinds Access Rights Manager installation by looking for the service in Windows Services (services.msc) or checking for installation directories typically under C:\Program Files\SolarWinds\Access Rights ManagerAffected if SolarWinds Access Rights Manager service or installation is found on the system
-
Determine installed versionOpen the Windows Services panel (services.msc), locate the SolarWinds Access Rights Manager service, right-click and select Properties to view the executable path, or check Add/Remove Programs for the version numberAffected if The installed version is 2023.2.4 or earlier (any version <= 2023.2.4)
-
Check network exposure of ARM web interfaceDetermine if the SolarWinds ARM web interface (typically on ports 8080 or 8443) is accessible from untrusted networks by reviewing firewall rules, NAT configurations, or performing a port scan from an external IPAffected if The ARM web interface is exposed to the internet or untrusted networks without proper access controls
-
Inspect web server logs for traversal patternsLocate and review IIS or SolarWinds ARM web server logs (typically in C:\ProgramData\SolarWinds\Logs or IIS log directories) for requests containing patterns like ../, ..\, or unusual file path access attemptsAffected if Log analysis reveals directory traversal attempts (such as ../../ or absolute path traversal) targeting sensitive system directories
You are affected if SolarWinds Access Rights Manager version 2023.2.4 or earlier is installed and its web interface is network-accessible, since the vulnerability can be exploited remotely without authentication.
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 immediately. If unavailable, restrict network exposure to the Access Rights Manager interface and implement WAF rules to block directory traversal patterns.
2023.2.5 or later (check SolarWinds official release notes for exact fixed version)
- Check the SolarWinds Access Rights Manager version currently installed
- Navigate to the official SolarWinds documentation at documentation.solarwinds.com or the SolarWinds release notes
- Locate the security advisory for CVE-2024-28992 to identify the specific fixed release version
- Upgrade to the fixed release version (typically a version higher than 2023.2.4)
- Verify the upgrade was successful and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28992 — 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-28992 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