CVE-2024-32498

Public on

Last Modified: UTC

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

Description

An input validation flaw was discovered in how multiple OpenStack services validate images with backing file references. An authenticated attacker could provide a malicious image via upload, or by creating and modifying an image from an existing volume. Validation of images can be triggered during image upload or when attaching images to virtual machines. During this process, the affected OpenStack services could be tricked into reading or writing to the host with the equivalent privileges of QEMU. This bypasses isolation restrictions, significantly reducing the security of an affected compute host, and could enable arbitrary code execution, a denial of service, or leaking of secrets. If exploited, the immediate impact is limited to an individual compute host. However, if the attacker has access to multiple hosts and enough time to repeat it, they could potentially spread across all compute hosts.

Statement

The vast majority of deployments of Red Hat OpenStack Platform should be assumed to be vulnerable as they are likely to be using at least one of the impacted services: Compute (nova), Block Storage (cinder), and Image (glance).

While an attacker must have valid login credentials to exploit this vulnerability, OpenStack supports multiple deployment scenarios with a variety of security postures. Open-cloud or multi-tenant deployments where infrastructure is shared by users who may be untrusted should treat this vulnerability as if it could be performed by an unauthenticated attacker. Considering this, along with the significant potential for disruption, we have rated the severity of this vulnerability as Critical.

The discovery of this vulnerability led to the discovery of an additional vulnerability (CVE-2024-4467) in QEMU. The impact to QEMU is significantly less as it is designed to only be run with trusted images. Red Hat OpenStack Platform is at a higher risk due from this underlying vulnerability, as OpenStack must tolerate running untrusted images.

Mitigation

Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.

Additional Information

External References

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

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

Content from bugs.launchpad.net is not included.https://bugs.launchpad.net/nova/+bug/2059809

Content from www.openwall.com is not included.https://www.openwall.com/lists/oss-security/2024/07/02/2

Affected Packages and Issued Red Hat Security Errata

Products / Services Components State Errata
Red Hat OpenStack Platform 10 (Newton) openstack-cinder Not affected
Red Hat OpenStack Platform 10 (Newton) openstack-glance Not affected
Red Hat OpenStack Platform 10 (Newton) openstack-nova Not affected
Red Hat OpenStack Platform 13 (Queens) openstack-cinder Not affected
Red Hat OpenStack Platform 13 (Queens) openstack-glance Not affected
Red Hat OpenStack Platform 13 (Queens) openstack-nova Not affected
Red Hat OpenStack Platform 16.1 openstack-cinder Fixed RHSA-2024:4425
Red Hat OpenStack Platform 16.1 openstack-glance Fixed RHSA-2024:4425
Red Hat OpenStack Platform 16.1 openstack-nova Fixed RHSA-2024:4425
Red Hat OpenStack Platform 16.2 openstack-cinder Fixed RHSA-2024:4273
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 8.8 6.5
Attack Vector Local Network
Attack Complexity Low Low
Privileges Required Low Low
User Interaction None None
Scope Changed Unchanged
Confidentiality Impact High High
Integrity Impact High None
Availability Impact High None

CVSS v3 Vector

Red Hat CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

NVD CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Red Hat CVSS v3 Score Explanation

After careful analysis of the subsequent flaw, it has been found that an attacker with access to multiple hosts can spread through lateral movement by writing files to those hosts and performing code execution in them, which is why the CVSS has been marked as such.

Acknowledgements

Red Hat would like to thank Martin Kaesberger for reporting this issue.

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.