Cyber Resilience

CVE-2024-25966

Dell Powerscale Onefs 8.2.0 – 9.3.0

Published
14 May 2024
Modified
20 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0092 57th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2024-25966 is a medium-severity Improper Handling of Unexpected Data Type (CWE-241) vulnerability in Dell Powerscale Onefs. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Dell PowerScale OneFS versions 8.2.x through 9.7.0.2 contains an improper handling of unexpected data type vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability, leading to denial of service.

CWE(s)
CWE-241NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-22471Same product: Dell Powerscale Onefs
CVE-2024-25970Same product: Dell Powerscale Onefs
CVE-2025-30102Same product: Dell Powerscale Onefs
CVE-2025-26479Same product: Dell Powerscale Onefs
CVE-2024-32853Same product: Dell Powerscale Onefs
CVE-2024-25967Same product: Dell Powerscale Onefs
CVE-2026-21424Same product: Dell Powerscale Onefs
CVE-2026-21426Same product: Dell Powerscale Onefs
CVE-2023-32486Same product: Dell Powerscale Onefs
CVE-2026-21421Same product: Dell Powerscale Onefs

Affected Assets

dell
powerscale onefs
8.2.0 — 9.3.0 · 9.4.0 — 9.4.0.18 · 9.5.0.0 — 9.5.0.8

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation explicitly checks that supplied data matches expected types and rejects mismatches before they reach processing logic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input validation and type checking to prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect type-handling flaws but does not itself implement the preventive control.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes input validation and type checking that directly mitigates improper handling of unexpected data types.

A.8.26 Application security requirements partial match
prevents

Application security requirements typically mandate strong input validation and type enforcement to prevent malformed data processing.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles encourage robust input handling but do not specifically address data-type validation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require type checking and input sanitization, directly addressing improper handling of unexpected data types.

References