CVE-2024-37143
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 Improper Link Resolution Before File Access vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability to execute arbitrary code on the system.
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 confidenceImproper Link Resolution Before File Access (symlink attack) vulnerability in Dell PowerFlex, InsightIQ, and Data Lakehouse allows an unauthenticated remote attacker to manipulate file system links to access unauthorized files or execute arbitrary code with elevated privileges.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 (Data Lakehouse, InsightIQ, PowerFlex Appliance Intelligent Catalog, PowerFlex Manager, or PowerFlex Rack) is running in your environment. Check the application name, service name, or documentation.Affected if The system runs any of the affected products: Data Lakehouse, InsightIQ, PowerFlex Appliance Intelligent Catalog, PowerFlex Manager, or PowerFlex Rack.
-
Determine Data Lakehouse versionLocate the Data Lakehouse installation directory or check the application version via its management interface or configuration file. Typical locations include /opt/dell/datalakehouse or the application's built-in version command.Affected if The installed version is lower than 1.2.0.0.
-
Determine InsightIQ versionLocate the InsightIQ installation directory or check the version via its web interface (usually port 8080 or 8443), or run 'iiq --version' from the installation bin directory.Affected if The installed version is lower than 5.1.1.
-
Determine PowerFlex Appliance Intelligent Catalog versionCheck the Intelligent Catalog version through the PowerFlex Manager interface or locate the IC version file in the appliance filesystem, typically under /opt/ic or similar vendor paths.Affected if The installed version is lower than 46.376.00.
-
Determine PowerFlex Manager versionCheck the PowerFlex Manager version through its administrative web interface (usually port 443) under 'About' or 'System Information', or locate the version file in the installation directory.Affected if The installed version is lower than 4.6.1.0.
-
Determine PowerFlex Rack Release Certification Matrix versionCheck the RCM version through the PowerFlex Rack management interface or locate the certification matrix version file in the appliance configuration.Affected if The installed version is >= 3.7.0.0 and < 3.7.6.0, OR >= 3.8.0.0 and < 3.8.1.0.
You are affected if any installed Dell product matches the specific version range listed above and the product handles external file inputs or allows file system link operations.
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
Apply vendor-supplied patches: upgrade PowerFlex appliance to IC 46.381.00 or IC 46.376.00, PowerFlex rack to RCM 3.8.1.0 (3.8.x) or RCM 3.7.6.0 (3.7.x), PowerFlex Manager to 4.6.1.0, InsightIQ to 5.1.1, and Data Lakehouse to 1.2.0.0.
Data Lakehouse: 1.2.0.0+ | InsightIQ: 5.1.1+ | PowerFlex Appliance IC: 46.376.00+ or 46.381.00+ | PowerFlex Manager: 4.6.1.0+ | PowerFlex Rack RCM 3.7.x: 3.7.6.0+ | PowerFlex Rack RCM 3.8.x: 3.8.1.0+
- For Data Lakehouse: Upgrade to version 1.2.0.0 or later
- For InsightIQ: Upgrade to version 5.1.1 or later
- For PowerFlex Appliance Intelligent Catalog: Upgrade to version 46.376.00 or later (also 46.381.00 addresses this issue)
- For PowerFlex Manager: Upgrade to version 4.6.1.0 or later
- For PowerFlex Rack Release Certification Matrix (3.7.x train): Upgrade to version 3.7.6.0 or later
- For PowerFlex Rack Release Certification Matrix (3.8.x train): Upgrade to version 3.8.1.0 or later
- Consult Dell support or official documentation for specific upgrade procedures and scheduling
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37143 — 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-37143 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