CVE-2023-43087
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 8.2.x, 9.0.0.x-9.5.0.x contains an improper handling of insufficient permissions. A low privileged remote attacker could potentially exploit this vulnerability to cause information disclosure.
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 8.2.x and 9.0.0.x-9.5.0.x contain an improper handling of insufficient permissions vulnerability. A low privileged remote attacker could potentially exploit improper permission validation to gain unauthorized access to sensitive information.
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>= 8.2.0, <= 8.2.2>= 9.2.1, < 9.2.1.24>= 9.4, < 9.4.0.15>= 9.5, < 9.5.0.6CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/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 the installed OneFS versionRun the 'isi version' command or check the OneFS web interface dashboard for the current firmware versionAffected if The version displayed falls within any of these ranges: 8.2.0-8.2.2, 9.2.1-9.2.1.23, 9.4.0-9.4.0.14, or 9.5.0-9.5.0.5
-
Confirm the exact minor version numberUse 'isi_get_versions' or access the support dashboard to retrieve the full version string including the build numberAffected if The full version string shows a version lower than 9.2.1.24, 9.4.0.15, or 9.5.0.6 within the respective branches
-
Review audit logs for unauthorized access attemptsCheck the OneFS audit logs under /var/log/audit/ or via the platform UI for failed permission checks from low-privileged accounts accessing restricted resourcesAffected if Logs show successful access to sensitive directories or files by accounts lacking explicit permissions for those resources
-
Verify access control configurationExamine the access zone permissions and sharing configurations using 'isi zone' and 'isi smb share' commands to identify any misconfigured ACLsAffected if Any share or directory exposes sensitive data to users without proper role-based access control assignments
You are affected if your OneFS version is 8.2.0 through 8.2.2, 9.2.1 through 9.2.1.23, 9.4.0 through 9.4.0.14, or 9.5.0 through 9.5.0.5, and you have low-privileged users who could potentially access restricted information.
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.2.1.249.4.0.159.5.0.6
Apply the vendor-provided patch or upgrade to a patched OneFS version. Review user permissions and access controls as part of remediation.
Upgrade to OneFS 9.2.1.24 (or later 9.2.1.x), 9.4.0.15 (or later 9.4.x), 9.5.0.6 (or later 9.5.x), or a later major version
- 1. Identify the current PowerScale OneFS version using 'isi version' or through the web admin console.
- 2. Based on the current version, plan upgrade path to the fixed release: For 8.2.x branches, upgrade to 9.2.1.24 or later; For 9.2.1.x, upgrade to 9.2.1.24 or later; For 9.4.x, upgrade to 9.4.0.15 or later; For 9.5.x, upgrade to 9.5.0.6 or later.
- 3. Review Dell PowerScale OneFS upgrade prerequisites and compatibility documentation at support.dell.com.
- 4. Create a backup of the current cluster configuration.
- 5. Schedule a maintenance window as upgrades require brief cluster downtime.
- 6. Download the appropriate OneFS iso/image from Dell Support.
- 7. Execute the upgrade following Dell's standard OneFS upgrade procedure (typically via 'isi升级' or web admin).
- 8. After upgrade completes, verify the new version matches the expected fixed release.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43087 — 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-43087 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