Cyber Resilience

CVE-2024-49602

Dell Powerscale Onefs 8.2.2 – 9.7.1.3

Published
09 December 2024
Modified
20 February 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0036 29th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2024-49602 is a medium-severity Multiple Unlocks of a Critical Resource (CWE-765) vulnerability in Dell Powerscale Onefs. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Dell PowerScale OneFS Versions 8.2.2.x through 9.8.0.x contain an improper resource unlocking vulnerability. A remote low privileged attacker could potentially exploit this vulnerability, leading to denial of service.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-32494Same product: Dell Powerscale Onefs
CVE-2025-43883Same product: Dell Powerscale Onefs
CVE-2025-43935Same product: Dell Powerscale Onefs
CVE-2024-53298Same product: Dell Powerscale Onefs
CVE-2026-49501Same product: Dell Powerscale Onefs
CVE-2024-32854Same product: Dell Powerscale Onefs
CVE-2024-37133Same product: Dell Powerscale Onefs
CVE-2024-39579Same product: Dell Powerscale Onefs
CVE-2025-26330Same product: Dell Powerscale Onefs
CVE-2025-43722Same product: Dell Powerscale Onefs

Affected Assets

dell
powerscale onefs
9.8.0.0 · 8.2.2 — 9.7.1.3 · 9.4.0 — 9.4.0.20 · 9.5.0.0 — 9.5.1.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover erroneous unlock sequences before deployment.

Security engineering principles include correct synchronization and resource-state management that stop multiple-unlock defects from being introduced.

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 enforce correct lock/unlock discipline and resource management.

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.

finds

Security testing in development can detect resource-state anomalies caused by multiple unlocks.

prevents

Secure development lifecycle practices can include resource-locking discipline and review to prevent multiple-unlock defects.

prevents

Application security requirements can mandate proper lock acquisition/release patterns.

prevents

Secure system architecture and engineering principles can mandate proper resource-state management and locking invariants.

prevents

Secure coding standards and reviews can catch or prevent erroneous unlock sequences in critical sections.

prevents

Change management may catch locking issues introduced by modifications but does not prevent the weakness itself.

References