CVE-2023-40058
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 · uneditedSensitive data was added to our public-facing knowledgebase that, if exploited, could be used to access components of Access Rights Manager (ARM) if the threat actor is in the same 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 confidenceSensitive data was inadvertently published to a public-facing knowledgebase. If a threat actor who has network proximity to the affected environment discovers this exposed data, they could potentially use it to gain unauthorized access to components of SolarWinds Access Rights Manager (ARM).
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.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Check installed SolarWinds ARM versionUse the SolarWinds ARM About or Version information panel within the application, or check the installed software list on the server where ARM is hostedAffected if The installed version is 2023.2.1 or any earlier version (2023.2.1 and below are affected)
-
Identify if a public-facing knowledgebase existsReview your SolarWinds ARM deployment configuration to determine whether a knowledgebase or help documentation system is accessible from external networks (public internet)Affected if A knowledgebase is publicly accessible without authentication or network restrictions
-
Audit publicly accessible documentation for sensitive dataExamine all publicly accessible knowledgebase articles, help docs, or support documentation for exposed credentials, API keys, passwords, connection strings, or configuration secretsAffected if Any credentials, keys, tokens, or configuration secrets are found in publicly accessible documentation
-
Review network exposure of ARM interfacesUse network scanning or firewall logs to identify which ARM interfaces (including knowledgebase portals) are exposed to untrusted networks or the internetAffected if The knowledgebase or any ARM management interface is reachable from external/untrusted networks
You are affected if SolarWinds ARM version is 2023.2.1 or lower AND a knowledgebase or documentation system is publicly accessible with sensitive data exposed.
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.
From vendor dataImmediately remove the sensitive data from the public knowledgebase and conduct a thorough audit of all publicly accessible documentation to ensure no additional credentials, keys, or configuration secrets remain exposed. Rotate any exposed credentials as a precautionary measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40058 — 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-2023-40058 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