CVE-2024-28991
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) was found to be susceptible to a remote code execution vulnerability. If exploited, this vulnerability would allow an authenticated user to abuse the service, resulting in 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 · moderate confidenceSolarWinds Access Rights Manager contains a remote code execution vulnerability that allows an authenticated user to abuse the service functionality to execute arbitrary code on the underlying system. This is a service-side vulnerability requiring valid credentials for exploitation.
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< 2024.3.1CVSS 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.
-
Confirm SolarWinds ARM is installedCheck system for SolarWinds Access Rights Manager components or services - look for SolarWinds ARM service, installation directory, or web application poolsAffected if SolarWinds Access Rights Manager software is present on the system
-
Identify installed ARM versionUse the SolarWinds ARM administrative interface, check the Windows Programs and Features list, or run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Access Rights Manager*'} | Select-Object DisplayName, DisplayVersionAffected if Version is lower than 2024.3.1 or version cannot be determined
-
Check if ARM web interface is accessibleAttempt to reach the ARM web portal internally: http://localhost:8080 or the configured host/port for your deploymentAffected if Web interface responds and accepts authentication
-
Verify service functionality is enabledReview ARM configuration to confirm the service functionality that allows code execution is not disabled or restrictedAffected if Service functionality is enabled and accessible to authenticated users
-
Identify accounts with ARM accessReview user accounts configured in ARM or check Active Directory integration for accounts with ARM permissionsAffected if Any valid user credentials exist that could be used to authenticate to ARM
Your environment is affected if SolarWinds Access Rights Manager is installed with a version prior to 2024.3.1 and the web interface or service functionality is accessible to authenticated users.
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 · scoped2024.3.1
Restrict ARM access to trusted authenticated users only, apply vendor-supplied patches immediately, and ensure principle of least privilege is enforced for all ARM accounts. Network segmentation can limit exposure to trusted internal networks.
2024.3.1
- Back up the current SolarWinds Access Rights Manager installation and configuration data
- Download Access Rights Manager version 2024.3.1 or later from the official SolarWinds download portal
- Follow the official SolarWinds upgrade documentation to install the fixed version
- After upgrade, verify the service is running correctly and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28991 — 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-28991 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