CVE-2023-43076
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 a denial-of-service vulnerability. A low privilege remote attacker could potentially exploit this vulnerability to cause an out of memory (OOM) condition.
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 a denial-of-service vulnerability where a low-privilege remote attacker can trigger an out-of-memory (OOM) condition, causing the storage system to become unavailable.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Determine PowerScale OneFS versionRun the OneFS CLI command 'isi version' or check through the OneFS web administration interface under Settings > AboutAffected if The installed version falls within these ranges: 8.2.0-8.2.2, 9.2.1 to below 9.2.1.24, 9.4.0 to below 9.4.0.15, or 9.5.0 to below 9.5.0.6
-
Verify management interface network exposureCheck firewall rules or networkACLs that control access to OneFS management ports (port 8080, 443, or custom HTTPS port) from untrusted networksAffected if The OneFS management interface (WebUI or SSH) is accessible from low-privilege or untrusted network segments without proper access controls
-
Confirm available memory baselineRun 'isi memory' CLI command or check memory utilization through the OneFS dashboard under Hardware > MemoryAffected if Memory utilization readings are unavailable or the system shows signs of memory exhaustion during normal operations
-
Check for OOM events in system logsReview OneFS logs using 'isi events -v' or check /var/log/messages for out-of-memory kill events or memory allocation failuresAffected if Recent system logs contain OOM-related events, memory allocation failures, or unexpected process terminations due to memory pressure
A system is affected if it runs OneFS versions 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 AND has its management interface exposed to an untrusted network where a low-privilege attacker could trigger the OOM condition.
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-supplied patch or upgrade to a fixed OneFS version. Until patched, restrict network access to the OneFS management interfaces and monitor memory utilization for anomalies.
8.2.3+ (or migrate to 9.x); 9.2.1.24+; 9.4.0.15+; 9.5.0.6+
- Verify current OneFS version by running 'isi version' or checking the web UI
- Review the upgrade path compatibility matrix at Dell Support for your current version
- For 8.2.x: Upgrade to 8.2.3 or later (or migrate to a supported 9.x branch)
- 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
- Schedule maintenance window as upgrades require cluster downtime
- Take a cluster configuration backup before upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43076 — 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-43076 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