CVE-2024-40767 — nova
MEDIUMCVE-2024-40767 is a medium-severity (CVSS 6.5) CWE-552 vulnerability in nova. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
OpenStack Nova vulnerable to unauthorized access to potentially sensitive data
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-40767.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
nova🐍nova🐍novaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | nova | all versions | No fix |
| 🐍PyPI | nova | ≥ 28.0.0 | No fix |
| 🐍PyPI | nova | ≥ 29.0.0 | No fix |
Affected Products
novaopenstackResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nova, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of nova for CVE-2024-40767. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability was rated with a severity of Important due to the potential to read sensitive information from a Nova compute host. This vulnerability was introduced as a result of the fixes for CVE-2024-32498 and only affects versions of Nova that include the patches for CVE-2024-32498.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 16.1 | openstack-nova-1:20.4.1-1.20221005193235.el8ost | RHSA-2024:5113 |
| Red Hat OpenStack Platform 16.2 | openstack-nova-1:20.6.2-2.20230814165229.el8ost | RHSA-2024:5097 |
| Red Hat OpenStack Platform 17.1 for RHEL 8 | openstack-nova-1:23.2.3-17.1.20231018123755.el8ost | RHSA-2024:5082 |
| Red Hat OpenStack Platform 17.1 for RHEL 9 | openstack-nova-1:23.2.3-17.1.20231018130829.el9ost | RHSA-2024:5083 |
Frequently Asked Questions
Is CVE-2024-40767 in your dependencies?
Find it across PyPI, including transitive dependencies.