CVE-2024-49603
Dell Powerscale Onefs 9.8.0.0 – 9.9.0.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-49603 is a medium-severity Function Call With Incorrectly Specified Argument Value (CWE-687) vulnerability in Dell Powerscale Onefs. Its CVSS base score is 4.3 (Medium).
Operationally, ranked at the 24th 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-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-43831
Vulnerability Data
Dell PowerScale OneFS Versions 8.2.2.x through 9.9.0.x contain an incorrect specified argument vulnerability. A remote low privileged legitimate user could potentially exploit this vulnerability, leading to information disclosure.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation activities can discover function calls that pass incorrect argument values.
Requiring documented development processes and coding standards can reduce the introduction of incorrect argument values.
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 (reviews, static analysis, testing) directly catch incorrect argument values during development.
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 incorrect argument values before release.
Secure development lifecycle includes code review and testing that can catch incorrect argument values.
Application security requirements can mandate input validation and argument checking.
Secure architecture principles promote defensive coding that reduces argument misuse.
Secure coding directly addresses correct function-call argument usage.