CVE-2024-23465
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 authentication bypass vulnerability. This vulnerability allows an unauthenticated user to gain domain admin access within the Active Directory environment.
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 authentication bypass vulnerability that allows an unauthenticated attacker to gain domain administrator privileges within the Active Directory environment, effectively granting full control over the domain.
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.
-
Verify SolarWinds Access Rights Manager installationCheck for the presence of SolarWinds Access Rights Manager in installed programs via Windows Programs and Features, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'SolarWinds' and 'Access Rights Manager'. Note the installed version number displayed.Affected if SolarWinds Access Rights Manager is installed and the version is 2023.2.4 or lower.
-
Confirm the exact installed versionIf the product is installed, determine the precise version number from the About section within the SolarWinds Access Rights Manager console, or from the registry key DisplayVersion under the product's uninstall entry.Affected if The version number is less than or equal to 2023.2.4.
-
Check if the ARM service is running and exposedOpen Windows Services and verify the SolarWinds Access Rights Manager service status. Determine if the service is listening on external network interfaces by reviewing the service binding configuration or running 'netstat -an | findstr :port' where port is the ARM service port (commonly 8080 or 8443).Affected if The service is running and bound to accessible network interfaces, especially if exposed beyond the internal network.
-
Review Active Directory integration configurationWithin the SolarWinds Access Rights Manager console, navigate to the Active Directory integration settings to confirm that domain connectivity is configured and the service has privileged access to the AD environment.Affected if The product is integrated with Active Directory and has elevated domain permissions.
If SolarWinds Access Rights Manager version 2023.2.4 or lower is installed, the service is running and network-accessible, and AD integration is active, the environment is affected by this authentication bypass vulnerability.
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 from SolarWinds immediately; until patched, consider network segmentation or disabling the affected service to reduce exposure.
2024.1 or later (any version > 2023.2.4)
- Download the latest version of SolarWinds Access Rights Manager from the official SolarWinds download portal
- Review the release notes for version 2024.1 or later for any specific migration or upgrade instructions
- Backup the current Access Rights Manager configuration and database
- Install the upgraded version following the standard upgrade procedure
- Verify that the authentication mechanism is properly functioning post-upgrade
- Confirm that domain admin access requires proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23465 — 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-23465 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