CVE-2024-49603
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 Versions 8.2.2.x through 9.9.0.x contain an incorrect specified argument vulnerability. A remote low privileged legitimate user could potentially exploit this vulnerability, leading to 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.2.x through 9.9.0.x contain an incorrect specified argument vulnerability that allows remote low-privileged users to exploit improper argument handling in some function or API call, leading to information disclosure.
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.8.0.0, < 9.9.0.1>= 8.2.2, < 9.7.1.3CVSS 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 PowerScale OneFS versionLog into the OneFS web interface and navigate to the 'Cluster > Overview' page, or run 'isi get version' via CLI. The version is displayed as a numeric string such as 9.7.0.0 or 9.8.0.0.Affected if The installed version falls within 8.2.2 to 9.7.1.2 (inclusive) OR within 9.8.0.0 to 9.9.0.0 (inclusive). Versions 9.7.1.3 through 9.7.x.x and version 9.9.0.1 and later are NOT affected.
-
Verify access to management interfacesCheck if the OneFS web UI (port 8080/443) or SSH access is exposed to untrusted networks. Review firewall rules or network ACLs controlling access to the cluster management IPs.Affected if The management interface is accessible from networks accessible to low-privileged users outside the authorized administrator group.
-
Check for low-privileged user accountsReview existing OneFS user accounts via the web UI under 'Access > Users' or by running 'isi auth users list' in CLI. Identify any accounts with read-only or non-administrative roles.Affected if Low-privileged (non-admin) user accounts exist in the system, as the vulnerability allows these users to trigger the improper argument handling.
You are affected if your OneFS version is between 8.2.2 and 9.7.1.2 inclusive, or between 9.8.0.0 and 9.9.0.0 inclusive, AND your management interface is accessible to low-privileged users.
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.7.1.39.9.0.1
Apply the vendor-supplied patch for Dell PowerScale OneFS when released. Restrict network access to the OneFS management interfaces to authorized personnel only as a temporary workaround.
OneFS 9.9.0.1 (for 9.x) or OneFS 9.7.1.3 (for 8.x to 9.x branch upgrade)
- 1. Identify the current PowerScale OneFS version by running 'isi version' or checking the web UI
- 2. For OneFS 9.8.0.0 through 9.9.0.0: Schedule a maintenance window and upgrade to OneFS 9.9.0.1 or later
- 3. For OneFS 8.2.2 through 9.7.1.2: Schedule a maintenance window and upgrade to OneFS 9.7.1.3 or later (note: 8.x releases require upgrade to 9.x branch)
- 4. After upgrade, verify the new version with 'isi version' and confirm the vulnerability is resolved
- 5. Review Dell PowerScale OneFS 9.9.0.1 release notes for any additional prerequisites or migration considerations
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-2024-49603 — 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-2024-49603 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