CVE-2023-2088
Description
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 highest impact is to confidentiality.
Statement
There are two ways this flaw can be triggered:
Intentional Type - A malicious user could use Cinder to detach their own volume. As Nova is not made aware of the situation, it might later grant the attacker access to a new volume of another user (later referred to as victim). As there are very little restrictions on how often this can be triggered and the victim might not have any way to identify if their volumes have been compromised, the impact to Cinder has been rated Critical.
Accident Type - This can occur if communication between Nova and Cinder is interrupted during a volume detachment process. A potential attacker seeking to exploit this type would need real-time access to logs and the ability to tamper with the private network. Due to these significant restrictions against triggering the vulnerability, components affected by this type are rated as Important.
Within Red Hat OpenStack Platform 13, it is not possible to eliminate the intentional type by code changes alone. Changes to policy and configuration are also required to restrict this vector. For details read the KCS article linked in the mitigation section.
Mitigation
Red Hat OpenStack Platform 13: https://access.redhat.com/solutions/7012184
Red Hat OpenStack Platform 16 and newer: https://access.redhat.com/solutions/7012327
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 9.1 | 6.5 | 6.5 |
| Attack Vector | Network | Network | Network |
| Attack Complexity | Low | Low | Low |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Changed | Unchanged | Unchanged |
| Confidentiality | High | High | High |
| Integrity Impact | Low | None | None |
| Availability Impact | Low | None | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L
NVD: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data; Read Memory
If the released resource is subsequently reused or reallocated, then a read operation on the original resource might access sensitive data that is associated with a different user or entity.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
When the resource is released, the software might modify some of its structure, or close associated channels (such as a file descriptor). When the software later accesses the resource as if it is valid, the resource might not be in an expected state, leading to resultant errors that may lead to a crash.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands; Modify Application Data; Modify Memory
When the resource is released, the software might modify some of its structure. This might affect logic in the sections of code that still assume the resource is active. If the released resource is related to memory and is used in a function call, or points to unexpected data in a write operation, then code execution may be possible upon subsequent accesses.
Acknowledgements
This issue was discovered by Gorka Eguileor (Red Hat) and Jan Wasilewski (Atman).
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
