CVE-2022-47512
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 information was stored in plain text in a file that is accessible by a user with a local account in Hybrid Cloud Observability (HCO)/ SolarWinds Platform 2022.4. No other versions are affected
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 information was stored in plain text in a file accessible to users with local account access in Hybrid Cloud Observability (HCO)/SolarWinds Platform version 2022.4 only. This represents a local information disclosure vulnerability where file permissions or storage mechanisms allow unauthorized reading of sensitive data.
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= 2022.4.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Identify installed SolarWinds Platform versionRun the SolarWinds Platform installer with version query, or check the Orion Product Catalog via the Administration menu in the web interface, or query the SolarWinds database for the exact version stringAffected if The installed version is exactly 2022.4.0 (this specific version only)
-
Locate configuration and storage filesInspect the SolarWinds Platform installation directory (typically C:\Program Files\SolarWinds\ or /opt/solarwinds/) and any subdirectories used for storing configuration, credentials, or application dataAffected if Sensitive configuration files exist in locations accessible to local non-privileged users
-
Examine file permissionsUse OS-native commands (icacls on Windows, ls -la on Linux) to inspect access controls on identified configuration and storage files. Verify that only authorized service accounts have read accessAffected if Files containing sensitive data are readable by standard user accounts or groups other than SYSTEM/Administrator or the SolarWinds service account
-
Inspect file contents for plain text secretsOpen identified configuration, storage, or credential files in a text editor and search for patterns indicating sensitive data (passwords=, connectionString, API key, credentials, secret tokens). Check whether this data appears in plain text rather than encrypted or hashedAffected if Sensitive information such as passwords, API keys, connection strings, or authentication tokens are stored in plain text within accessible files
A user is affected if they are running exactly SolarWinds Platform version 2022.4.0 AND have configuration or storage files containing plain text sensitive data that are readable by non-privileged local accounts.
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 dataUpgrade to a patched version of SolarWinds Platform (contact vendor for availability) and audit file storage locations for any plain text sensitive data that should be encrypted or protected.
- 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-2022-47512 — 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-2022-47512 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