CVE-2024-37144
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 PowerFlex appliance versions prior to IC 46.381.00 and IC 46.376.00, Dell PowerFlex rack versions prior to RCM 3.8.1.0 (for RCM 3.8.x train) and prior to RCM 3.7.6.0 (for RCM 3.7.x train), Dell PowerFlex custom node using PowerFlex Manager versions prior to 4.6.1.0, Dell InsightIQ versions prior to 5.1.1, and Dell Data Lakehouse versions prior to 1.2.0.0 contain an Insecure Storage of Sensitive Information vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to information disclosure. The attacker may be able to use information disclosed to gain unauthorized access to pods within the cluster.
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 · high confidenceDell PowerFlex and related products store sensitive information insecurely, allowing a high-privileged local attacker to access stored credentials or secrets. The exposed information can then be leveraged to gain unauthorized access to Kubernetes pods within the cluster.
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< 1.2.0.0< 5.1.1< 46.376.00< 4.6.1.0>= 3.7.0.0, < 3.7.6.0>= 3.8.0.0, < 3.8.1.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Identify the installed Dell productDetermine which Dell product from the affected list is deployed in your environment (Data Lakehouse, InsightIQ, PowerFlex Appliance Intelligent Catalog, PowerFlex Manager, or PowerFlex Rack)Affected if The product is one of: Dell Data Lakehouse, Dell InsightIQ, Dell PowerFlex Appliance Intelligent Catalog, Dell PowerFlex Manager, or Dell PowerFlex Rack Release Certification Matrix
-
Determine the installed versionUse the product's management interface, CLI tool, or system information command to retrieve the current version numberAffected if The version cannot be determined or is lower than the patched versions listed
-
Compare version against affected ranges for Data LakehouseIf Data Lakehouse is installed, check if version is < 1.2.0.0Affected if Installed version is < 1.2.0.0
-
Compare version against affected ranges for InsightIQIf InsightIQ is installed, check if version is < 5.1.1Affected if Installed version is < 5.1.1
-
Compare version against affected ranges for PowerFlex Appliance Intelligent CatalogIf PowerFlex Appliance Intelligent Catalog is installed, check if version is < 46.376.00Affected if Installed version is < 46.376.00
-
Compare version against affected ranges for PowerFlex ManagerIf PowerFlex Manager is installed, check if version is < 4.6.1.0Affected if Installed version is < 4.6.1.0
You are affected if you have any of the listed Dell products installed and the installed version falls within the specified vulnerable ranges, as insecurely stored credentials could be accessible to high-privileged local attackers.
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 · scoped1.2.0.03.7.6.03.8.1.0
Update to the patched versions: IC 46.381.00 or IC 46.376.00 for PowerFlex appliance; RCM 3.8.1.0 (for 3.8.x) or RCM 3.7.6.0 (for 3.7.x) for PowerFlex rack; PowerFlex Manager 4.6.1.0; InsightIQ 5.1.1; Data Lakehouse 1.2.0.0.
Product-specific: IC 46.381.00/46.376.00 (Appliance), RCM 3.8.1.0 or 3.7.6.0 (Rack), PowerFlex Manager 4.6.1.0, InsightIQ 5.1.1, Data Lakehouse 1.2.0.0
- 1. Identify the specific Dell PowerFlex product in your environment (PowerFlex Appliance, PowerFlex Rack, PowerFlex Manager, InsightIQ, or Data Lakehouse)
- 2. Determine the current installed version of the affected product
- 3. For PowerFlex Appliance: upgrade to Intelligent Catalog (IC) version 46.381.00 or 46.376.00
- 4. For PowerFlex Rack: upgrade to Release Certification Matrix (RCM) version 3.8.1.0 (for 3.8.x train) or 3.7.6.0 (for 3.7.x train)
- 5. For PowerFlex Manager: upgrade to version 4.6.1.0 or later
- 6. For InsightIQ: upgrade to version 5.1.1 or later
- 7. For Data Lakehouse: upgrade to version 1.2.0.0 or later
- 8. After upgrade, verify the sensitive information storage has been properly secured and review access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37144 — 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-37144 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