Security Resilience

CVE-2023-2088

Redhat Openstack

Published
12 May 2023
Modified
04 November 2025
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:H/I:N/A:N
EPSS Score 0.012 68th percentile
Risk Priority 53 floored blend · peak EPSS

CVSS 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

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

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-6121Same vendor: Redhat
CVE-2026-9087Same vendor: Redhat
CVE-2024-1459Same vendor: Redhat
CVE-2025-12150Same vendor: Redhat
CVE-2026-4325Same vendor: Redhat
CVE-2026-7307Same vendor: Redhat
CVE-2026-54100Same vendor: Redhat
CVE-2026-16106Same vendor: Redhat
CVE-2026-9793Same vendor: Redhat
CVE-2023-4910Same vendor: Redhat

Affected Assets

redhat
openstack
all versions

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.

addresses: CWE-440

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.

ID.IM-02 partial match
blocks

Security testing and exercises help discover behavior deviations before deployment.

ID.RA-01 partial match
blocks

Vulnerability identification can surface spec-violating flaws, while eliminating the weakness reduces some vulnerability backlog.

PR.PS-02 partial match
blocks

Routine software maintenance and patching can remediate discovered specification violations.

PR.PS-06 partial match
blocks

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.

blocks

Secure development life cycle mandates verification against specifications, directly reducing expected-behavior violations.

blocks

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.

prevents

Secure coding practices enforce adherence to functional specifications during implementation.

finds

Security testing in development and acceptance validates that functions behave as specified.

References