# CVE-2024-32498: OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access > Authenticated users can read arbitrary server files via crafted QCOW2 images in OpenStack Cinder, Glance, and Nova, exposing sensitive data. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Jul 2024 - **Updated:** 4 Nov 2025 - **Also known as:** DEBIAN-CVE-2024-32498, DLA-3872-1, DLA-3873-1, DSA-5754-1, DSA-5755-1, DSA-5756-1, GHSA-r4v4-w9pv-6fph, PYSEC-2026-1708, PYSEC-2026-2414, PYSEC-2026-2493, RHSA-2024:4272, RHSA-2024:4273, RHSA-2024:4274, RHSA-2024:4425, UBUNTU-CVE-2024-32498, USN-6882-1, USN-6883-1, USN-6884-1 ## What is CVE-2024-32498? CVE-2024-32498 is a medium-severity path traversal vulnerability in n/a, published on 5 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description An issue was discovered in OpenStack Cinder through 24.0.0, Glance before 28.0.2, and Nova before 29.0.3. Arbitrary file access can occur via custom QCOW2 external data. By supplying a crafted QCOW2 image that references a specific data file path, an authenticated user may convince systems to return a copy of that file's contents from the server, resulting in unauthorized access to potentially sensitive data. All Cinder and Nova deployments are affected; only Glance deployments with image conversion enabled are affected. Weakness: CWE-552 (Files or Directories Accessible to External Parties) ## Which versions are affected by CVE-2024-32498? 9 open source packages ship an affected version, including cinder, glance and nova. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `cinder` | PyPI | All versions to 24.0.0 | None | | `cinder` | PyPI | All versions to 24.0.0 | None | | `cinder` | PyPI | All versions to 24.0.0 | None | | `glance` | PyPI | All versions to 28.0.1 | None | | `glance` | PyPI | All versions to 28.0.1 | None | | `glance` | PyPI | All versions to 28.0.1 | None | | `nova` | PyPI | All versions to 29.0.2 | None | | `nova` | PyPI | All versions to 29.0.2 | None | | `nova` | PyPI | All versions to 29.0.2 | None | | `openstack-cinder` | Red Hat:openstack:16.1::el8 | All versions | 1:15.4.0-1.20230510003503.el8ost | | `openstack-glance` | Red Hat:openstack:16.1::el8 | All versions | 1:19.0.4-1.20230310213451.el8ost | | `openstack-nova` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-api` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-common` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-compute` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-conductor` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-console` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-migration` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-novncproxy` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-scheduler` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-serialproxy` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-nova-spicehtml5proxy` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `python3-cinder` | Red Hat:openstack:16.1::el8 | All versions | 1:15.4.0-1.20230510003503.el8ost | | `python3-glance` | Red Hat:openstack:16.1::el8 | All versions | 1:19.0.4-1.20230310213451.el8ost | | `python3-nova` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193234.el8ost | | `openstack-cinder` | Red Hat:openstack:16.2::el8 | All versions | 1:15.6.1-2.20230906144858.el8ost | | `openstack-glance` | Red Hat:openstack:16.2::el8 | All versions | 1:19.0.5-2.20230310205021.el8ost | | `openstack-nova` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-api` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-common` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-compute` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-conductor` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-console` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-migration` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-novncproxy` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-scheduler` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-serialproxy` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `openstack-nova-spicehtml5proxy` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165228.el8ost | | `python3-cinder` | Red Hat:openstack:16.2::el8 | All versions | 1:15.6.1-2.20230906144858.el8ost | | `python3-glance` | Red Hat:openstack:16.2::el8 | All versions | 1:19.0.5-2.20230310205021.el8ost | Products: Openstack Cinder, Openstack Glance, Openstack Nova. ## How do I fix CVE-2024-32498? Apply the vendor's patch. ## Is CVE-2024-32498 being exploited? There is no known exploitation of CVE-2024-32498 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2015-5162](https://insights.sbomify.com/CVE-2015-5162/): OpenStack Cinder, Glance, and Nova contain Uncontrolled Resource Consumption (high 7.5) - [CVE-2017-15139](https://insights.sbomify.com/CVE-2017-15139/): Information disclosure in openstack-cinder (medium 5.1) - [CVE-2014-3641](https://insights.sbomify.com/CVE-2014-3641/): OpenStack Cinder Exposure of Sensitive Information to an Unauthorized Actor vulnerability (medium 4.0) - [CVE-2014-7231](https://insights.sbomify.com/CVE-2014-7231/): OpenStack Oslo utility sensitive information exposure via log files (low 2.1) - [CVE-2013-4183](https://insights.sbomify.com/CVE-2013-4183/): OpenStack Cinder LVMVolumeDriver does not zero deleted snapshots (low 2.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-32498 and fix it if it is affected. What it is: CVE-2024-32498 is a medium-severity path traversal vulnerability in n/a, published on 5 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-32498 in the wild and no public exploit code. Affected packages and fixed versions: - cinder (PyPI): affected all versions up to 24.0.0; no fix listed - cinder (PyPI): affected all versions up to 24.0.0; no fix listed - cinder (PyPI): affected all versions up to 24.0.0; no fix listed - glance (PyPI): affected all versions up to 28.0.1; no fix listed - glance (PyPI): affected all versions up to 28.0.1; no fix listed - glance (PyPI): affected all versions up to 28.0.1; no fix listed - nova (PyPI): affected all versions up to 29.0.2; no fix listed - nova (PyPI): affected all versions up to 29.0.2; no fix listed - nova (PyPI): affected all versions up to 29.0.2; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-32498/ (Markdown: https://insights.sbomify.com/CVE-2024-32498/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32498 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32498 - OSV: https://osv.dev/vulnerability/CVE-2024-32498 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32498/ Summaries are generated and may contain mistakes; the official description above is the record.