CVE-2024-23473
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 contain a hard-coded credential authentication bypass vulnerability. If exploited, this vulnerability allows access to the RabbitMQ management console. We thank Trend Micro Zero Day Initiative (ZDI) for its ongoing partnership in coordinating with SolarWinds on responsible disclosure of this and other potential vulnerabilities.
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 hard-coded credential vulnerability that allows authentication bypass to the RabbitMQ management console. An attacker with network access to the RabbitMQ service can use these embedded credentials to gain unauthorized administrative access to the message broker.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify installed SolarWinds Access Rights Manager versionCheck the installed version of SolarWinds Access Rights Manager through the application GUI, Windows Programs and Features, or the SolarWinds ARM installation directory. Compare the version number against the affected range (versions prior to 2023.2.4).Affected if The installed version is earlier than 2023.2.4
-
Determine if RabbitMQ management console is network accessibleVerify whether the RabbitMQ management interface ports (typically 15672 for HTTP or 15671 for HTTPS) are exposed to the network. Use netstat, firewall rules, or network scanning tools to check for listening services on these ports.Affected if RabbitMQ management console ports are listening and accessible from untrusted network segments
-
Locate RabbitMQ configuration filesSearch the SolarWinds Access Rights Manager installation directory for RabbitMQ configuration files, particularly rabbitmq.config or advanced.config, and any associated password or credential configuration files.Affected if Configuration files contain hard-coded credentials or embedded password values not managed through secure credential storage
-
Review RabbitMQ users for unauthorized administrative accountsQuery the RabbitMQ management interface or use rabbitmqctl list_users to enumerate all registered users. Check for unexpected or undocumented administrative users that may correspond to the hard-coded credentials.Affected if Unexpected administrative users exist in RabbitMQ that were not created by your organization
You are affected if SolarWinds Access Rights Manager version is below 2023.2.4 AND the RabbitMQ management console is network-accessible, as the hard-coded credentials could allow unauthorized administrative access.
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 · scoped2023.2.4
Immediately restrict RabbitMQ management console network exposure, rotate any compromised credentials, and apply vendor-provided patches when available. Consider implementing proper credential management and avoiding hard-coded credentials in production systems.
2023.2.4 or later
- 1. Identify the current version of SolarWinds Access Rights Manager by accessing the admin console or checking the installed software
- 2. Backup all current configuration data and user settings before proceeding with the upgrade
- 3. Download SolarWinds Access Rights Manager version 2023.2.4 or the latest stable version from the official SolarWinds download portal
- 4. Stop the Access Rights Manager services to ensure a clean upgrade process
- 5. Install the upgrade following the standard SolarWinds upgrade procedure documented in the official documentation
- 6. After installation, start the Access Rights Manager services
- 7. Verify the upgrade was successful by checking the version number in the admin interface
- 8. Confirm that the hard-coded credential vulnerability has been addressed by verifying access controls to the RabbitMQ management console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23473 — 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-23473 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