Nova: Metadata queries from Neutron to Nova are not restricted by tenant
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenStack 4 for RHEL 6 | |||
| openstack-neutron-0:2013.2.1-4.el6ost | cpe:/a:redhat:openstack:4::el6 | RHSA-2014:0091 | 2014-01-22T00:00:00Z |
| openstack-nova-0:2013.2.2-2.el6ost | cpe:/a:redhat:openstack:4::el6 | RHSA-2014:0231 | 2014-03-04T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-1885 | Interaction error in OpenStack Nova and Neutron before Havana 2013.2.1 and icehouse-1 does not validate the instance ID of the tenant making a request, which allows remote tenants to obtain sensitive metadata by spoofing the device ID that is bound to a port, which is not properly handled by (1) api/metadata/handler.py in Nova and (2) the neutron-metadata-agent (agent/metadata/agent.py) in Neutron. |
Github GHSA |
GHSA-22w9-j288-8p9w | OpenStack Nova Router metadata queries are not restricted by tenant |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.9% (1.852% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.