CVE-2023-2088

Public on

Last Modified: UTC

Critical Critical Impact What does this mean?
9.1 CVSS v3 Base Score

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

Additional Information

External References

Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2023-2088

Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2023-2088

Content from bugs.launchpad.net is not included.https://bugs.launchpad.net/bugs/2004555

Content from github.com is not included.https://github.com/advisories/GHSA-fvf4-jv3j-73mq

Content from security.openstack.org is not included.https://security.openstack.org/ossa/OSSA-2023-003.html

Affected Packages and Issued Red Hat Security Errata

Products / Services Components State Errata
Red Hat OpenStack Platform 13 (Queens) openstack-cinder Will not fix
Red Hat OpenStack Platform 13.0 (Queens) for RHEL 7.6 EUS openstack-nova Fixed RHSA-2023:3161
Red Hat OpenStack Platform 13.0 (Queens) for RHEL 7.6 EUS python-glance-store Fixed RHSA-2023:3161
Red Hat OpenStack Platform 13.0 (Queens) for RHEL 7.6 EUS python-os-brick Fixed RHSA-2023:3161
Red Hat OpenStack Platform 13.0 - ELS openstack-nova Fixed RHSA-2023:3161
Red Hat OpenStack Platform 13.0 - ELS python-glance-store Fixed RHSA-2023:3161
Red Hat OpenStack Platform 13.0 - ELS python-os-brick Fixed RHSA-2023:3161
Red Hat OpenStack Platform 16.1 openstack-cinder Fixed RHSA-2023:3156
Red Hat OpenStack Platform 16.1 openstack-nova Fixed RHSA-2023:3156
Red Hat OpenStack Platform 16.1 python-glance-store Fixed RHSA-2023:3156
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.

Common Vulnerability Scoring System (CVSS) Score Details

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 Authorities (CNA) source for its products and services (see Red Hat classifications ).

CVSS v3 Score Breakdown Red Hat NVD
CVSS v3 Base Score 9.1 6.5
Attack Vector Network Network
Attack Complexity Low Low
Privileges Required Low Low
User Interaction None None
Scope Changed Unchanged
Confidentiality Impact High High
Integrity Impact Low None
Availability Impact Low None

CVSS v3 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

Acknowledgements

This issue was discovered by Gorka Eguileor (Red Hat) and Jan Wasilewski (Atman).

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

 For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

 A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

 A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

 A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

 The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

 In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our This content is not included.Red Hat Vulnerability Scanner Certification program.