CVE-2024-49602
Dell Powerscale Onefs 8.2.2 – 9.7.1.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HSummary
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
- 🇪🇺 ENISA EUVD: EUVD-2024-43830
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
CVEs Like This One
Affected Assets
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.
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.
Security testing in development can detect resource-state anomalies caused by multiple unlocks.
Secure development lifecycle practices can include resource-locking discipline and review to prevent multiple-unlock defects.
Application security requirements can mandate proper lock acquisition/release patterns.
Secure system architecture and engineering principles can mandate proper resource-state management and locking invariants.
Secure coding standards and reviews can catch or prevent erroneous unlock sequences in critical sections.
Change management may catch locking issues introduced by modifications but does not prevent the weakness itself.