# CVE-2024-40767: OpenStack Nova vulnerable to unauthorized access to potentially sensitive data > An authenticated user can read arbitrary server files by uploading crafted images with backing file paths in OpenStack Nova. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **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:** 24 Jul 2024 - **Updated:** 4 Nov 2025 - **Also known as:** GHSA-rm86-h44c-2r2m, PYSEC-2026-1709, RHSA-2024:5083, RHSA-2024:5097, RHSA-2024:5113, UBUNTU-CVE-2024-40767, USN-6911-1 ## What is CVE-2024-40767? CVE-2024-40767 is a medium-severity path traversal vulnerability in n/a, published on 24 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description In OpenStack Nova before 27.4.1, 28 before 28.2.1, and 29 before 29.1.1, by supplying a raw format image that is actually a crafted QCOW2 image with a backing file path or VMDK flat image with a descriptor file path, an authenticated user may convince systems to return a copy of the referenced file's contents from the server, resulting in unauthorized access to potentially sensitive data. All Nova deployments are affected. NOTE: this issue exists because of an incomplete fix for CVE-2022-47951 and CVE-2024-32498. Weakness: CWE-552 (Files or Directories Accessible to External Parties) ## Which versions are affected by CVE-2024-40767? 7 open source packages ship an affected version, including nova and Nova. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `nova` | PyPI | All versions to 27.4.0 | None | | `nova` | PyPI | All versions to 27.4.0 | None | | `nova` | PyPI | From 28.0.0 to 28.2.0 | None | | `nova` | PyPI | From 29.0.0 to 29.1.0 | None | | `Nova` | PyPI | All versions to 27.4.0 | None | | `Nova` | PyPI | From 28.0.0 to 28.2.0 | None | | `Nova` | PyPI | From 29.0.0 to 29.1.0 | None | | `openstack-nova` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-api` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-common` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-compute` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-conductor` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-console` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-migration` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-novncproxy` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-scheduler` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-serialproxy` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova-spicehtml5proxy` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `python3-nova` | Red Hat:openstack:16.1::el8 | All versions | 1:20.4.1-1.20221005193235.el8ost | | `openstack-nova` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-api` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-common` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-compute` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-conductor` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-console` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-migration` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-novncproxy` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-scheduler` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-serialproxy` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova-spicehtml5proxy` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `python3-nova` | Red Hat:openstack:16.2::el8 | All versions | 1:20.6.2-2.20230814165229.el8ost | | `openstack-nova` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | | `openstack-nova-api` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | | `openstack-nova-common` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | | `openstack-nova-compute` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | | `openstack-nova-conductor` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | | `openstack-nova-migration` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | | `openstack-nova-novncproxy` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | | `openstack-nova-scheduler` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | | `openstack-nova-serialproxy` | Red Hat:openstack:17.1::el9 | All versions | 1:23.2.3-17.1.20231018130829.el9ost | Products: Openstack Nova. ## How do I fix CVE-2024-40767? Upgrade to a fixed version. ## Is CVE-2024-40767 being exploited? There is no known exploitation of CVE-2024-40767 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2017-7214](https://insights.sbomify.com/CVE-2017-7214/): OpenStack Nova logs sensitive context from notification exceptions (critical 9.8) - [CVE-2017-17051](https://insights.sbomify.com/CVE-2017-17051/): OpenStack Nova DoS by rebuilding the same instance with a new image multiple times (high 8.6) - [CVE-2020-17376](https://insights.sbomify.com/CVE-2020-17376/): OpenStack Nova Live migration fails to update persistent domain XML (high 8.3) - [CVE-2017-18191](https://insights.sbomify.com/CVE-2017-18191/): OpenStack Nova Denial of service attack on the compute host (high 7.5) - [CVE-2015-3280](https://insights.sbomify.com/CVE-2015-3280/): OpenStack Compute (nova) allows remote authenticated users to cause a denial of service (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-40767 and fix it if it is affected. What it is: CVE-2024-40767 is a medium-severity path traversal vulnerability in n/a, published on 24 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-40767 in the wild and no public exploit code. Affected packages and fixed versions: - nova (PyPI): affected all versions up to 27.4.0; no fix listed - nova (PyPI): affected all versions up to 27.4.0; no fix listed - nova (PyPI): affected from 28.0.0 up to 28.2.0; no fix listed - nova (PyPI): affected from 29.0.0 up to 29.1.0; no fix listed - Nova (PyPI): affected all versions up to 27.4.0; no fix listed - Nova (PyPI): affected from 28.0.0 up to 28.2.0; no fix listed - Nova (PyPI): affected from 29.0.0 up to 29.1.0; 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-40767/ (Markdown: https://insights.sbomify.com/CVE-2024-40767/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-40767 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-40767 - OSV: https://osv.dev/vulnerability/CVE-2024-40767 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-40767/ Summaries are generated and may contain mistakes; the official description above is the record.