CVE-2023-2088
Redhat Openstack
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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-2023-2088 is a medium-severity Expected Behavior Violation (CWE-440) vulnerability in Redhat Openstack. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 32% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-33614
Vulnerability Data
A flaw was found in OpenStack due to an inconsistency between Cinder and Nova. This issue can be triggered intentionally or by accident. A remote, authenticated attacker could exploit this vulnerability by detaching one of their volumes from Cinder. The…
more
highest impact is to confidentiality.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
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.
Verification of security function operation directly detects deviations from expected behavior.
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.
Security testing and exercises help discover behavior deviations before deployment.
Vulnerability identification can surface spec-violating flaws, while eliminating the weakness reduces some vulnerability backlog.
Routine software maintenance and patching can remediate discovered specification violations.
Secure SDLC practices directly enforce specification compliance and catch expected-behavior violations 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.
Secure development life cycle mandates verification against specifications, directly reducing expected-behavior violations.
A.8.26 only requires that security requirements (including resilience against attacks like injections) be identified and specified during development or acquisition; it does not itself enforce, implement or assure those requirements, so the expected-behavior violation can still arise and be exploited.
Secure coding practices enforce adherence to functional specifications during implementation.
Security testing in development and acceptance validates that functions behave as specified.