CVE-2023-22575
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 · uneditedDell PowerScale OneFS 9.0.0.x - 9.4.0.x contain an insertion of sensitive information into log file vulnerability in celog. A low privileges user could potentially exploit this vulnerability, leading to information disclosure and escalation of privileges.
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 confidenceDell PowerScale OneFS versions 9.0.0.x through 9.4.0.x contain a vulnerability in the celog component where sensitive information is being written to log files. Low-privilege users who have access to these logs can view this sensitive data, potentially obtaining credentials or tokens that enable privilege escalation.
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>= 9.1.0.0, < 9.1.0.27>= 9.2.1.0, < 9.2.1.20>= 9.4.0.0, < 9.4.0.11CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Check PowerScale OneFS versionRun 'isi version' or 'isi_get_versions' command to retrieve the installed OneFS versionAffected if The installed version falls within 9.1.0.0 through 9.1.0.26, 9.2.1.0 through 9.2.1.19, or 9.4.0.0 through 9.4.0.10
-
Locate celog component log filesSearch for celog-related log files in the OneFS log directory structure (typically under /var/log/ or /ifs/var/log/) using 'find /var/log -iname "*celog*"' or consult OneFS documentation for celog file locationsAffected if Celog log files exist on the system
-
Inspect celog logs for sensitive dataUse 'grep -i' to search celog log files for patterns indicating sensitive information such as 'password', 'token', 'secret', 'key', 'credential', or API keysAffected if Sensitive strings such as passwords, tokens, or credentials appear in celog log output
-
Verify log file access permissionsRun 'ls -la' on celog log files to check group and world read permissions, and identify which users and groups have accessAffected if Non-privileged or low-privilege users have read access to celog log files
The system is affected if running a vulnerable OneFS version AND celog logs contain sensitive information AND low-privilege users can read those log files.
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 · scoped9.1.0.279.2.1.209.4.0.11
Apply the vendor patch when available; until then, restrict access to celog log files to privileged users only and monitor for unauthorized access to sensitive log data.
Upgrade to 9.1.0.27 or later (for 9.1.x), 9.2.1.20 or later (for 9.2.x), or 9.4.0.11 or later (for 9.4.x)
- 1. Identify the current PowerScale OneFS version by running 'isi version' or checking the web admin console.
- 2. Determine which version branch your current installation is on (9.1.x, 9.2.x, or 9.4.x).
- 3. For version 9.1.0.0 - 9.1.0.26: Plan upgrade to version 9.1.0.27 or later.
- 4. For version 9.2.1.0 - 9.2.1.19: Plan upgrade to version 9.2.1.20 or later.
- 5. For version 9.4.0.0 - 9.4.0.10: Plan upgrade to version 9.4.0.11 or later.
- 6. Review Dell PowerScale OneFS upgrade documentation and release notes for prerequisites.
- 7. Create a backup of cluster configuration and verify data integrity before upgrading.
- 8. Schedule maintenance window as upgrade may require cluster restart.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.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,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22575 — 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-22575 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