CVE-2023-36490
Intel Memory And Storage Tool ≤ 2.3
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:HSummary
CVE-2023-36490 is a medium-severity Improper Initialization (CWE-665) vulnerability in Intel Memory And Storage Tool. Its CVSS base score is 5.0 (Medium).
Operationally, ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-40439
Vulnerability Data
Improper initialization in some Intel(R) MAS software before version 2.3 may allow an authenticated user to potentially enable denial of service via local access.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Ensures shared resources are explicitly initialized or cleared on allocation, preventing exposure of prior contents to new users or processes.
Mandates that every instance begins in a known (presumably clean) state, eliminating reliance on residual or uninitialized state left by prior executions.
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 proper resource initialization during coding and testing.
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 can detect uninitialized variables but does not itself enforce initialization practices.
Configuration management can enforce secure defaults and initialization settings but is not the primary control for code-level initialization.
Secure development life cycle mandates initialization checks and secure defaults that directly prevent improper resource initialization.
Secure system architecture and engineering principles require explicit initialization of resources and secure state management.
Secure coding standards explicitly forbid uninitialized variables and mandate proper resource initialization before use.