| 2019-08-29 13:16:07 |
Kobi Samoray |
bug |
|
|
added bug |
| 2019-08-29 13:16:44 |
Kobi Samoray |
nova: assignee |
|
Kobi Samoray (ksamoray) |
|
| 2019-08-29 14:27:16 |
Jeremy Stanley |
description |
While querying metadata from an instance via a loadbalancer, metadata service relies on X-Metadata-Provider to identify the correct instance by querying Neutron for subnets which are attached to the loadbalancer.
Then the subnet result is used to identify the instance by querying for ports which are attached to the subnets above.
Yet, when the first query result is empty due to deletion, bug or any other reason within the Neutron side, this may cause a security vulnerability, as Neutron will retrieve ports of _any_ instance which has the same IP address as the instance which is queried.
That could compromise key pairs and other sensitive data. |
This issue is being treated as a potential security risk under embargo. Please do not make any public mention of embargoed (private) security vulnerabilities before their coordinated publication by the OpenStack Vulnerability Management Team in the form of an official OpenStack Security Advisory. This includes discussion of the bug or associated fixes in public forums such as mailing lists, code review systems and bug trackers. Please also avoid private disclosure to other individuals not already approved for access to this information, and provide this same reminder to those who are made aware of the issue prior to publication. All discussion should remain confined to this private bug report, and any proposed fixes should be added to the bug as attachments.
While querying metadata from an instance via a loadbalancer, metadata service relies on X-Metadata-Provider to identify the correct instance by querying Neutron for subnets which are attached to the loadbalancer.
Then the subnet result is used to identify the instance by querying for ports which are attached to the subnets above.
Yet, when the first query result is empty due to deletion, bug or any other reason within the Neutron side, this may cause a security vulnerability, as Neutron will retrieve ports of _any_ instance which has the same IP address as the instance which is queried.
That could compromise key pairs and other sensitive data. |
|
| 2019-08-29 14:27:27 |
Jeremy Stanley |
bug task added |
|
ossa |
|
| 2019-08-29 14:27:36 |
Jeremy Stanley |
ossa: status |
New |
Incomplete |
|
| 2019-08-29 14:27:49 |
Jeremy Stanley |
bug |
|
|
added subscriber Nova Core security contacts |
| 2019-09-05 14:49:35 |
Jeremy Stanley |
information type |
Private Security |
Public |
|
| 2019-09-05 14:49:46 |
Jeremy Stanley |
ossa: status |
Incomplete |
Won't Fix |
|
| 2019-09-05 14:50:01 |
Jeremy Stanley |
tags |
|
security |
|
| 2019-09-05 15:06:58 |
OpenStack Infra |
nova: status |
New |
In Progress |
|
| 2019-09-05 17:15:23 |
Jeremy Stanley |
description |
This issue is being treated as a potential security risk under embargo. Please do not make any public mention of embargoed (private) security vulnerabilities before their coordinated publication by the OpenStack Vulnerability Management Team in the form of an official OpenStack Security Advisory. This includes discussion of the bug or associated fixes in public forums such as mailing lists, code review systems and bug trackers. Please also avoid private disclosure to other individuals not already approved for access to this information, and provide this same reminder to those who are made aware of the issue prior to publication. All discussion should remain confined to this private bug report, and any proposed fixes should be added to the bug as attachments.
While querying metadata from an instance via a loadbalancer, metadata service relies on X-Metadata-Provider to identify the correct instance by querying Neutron for subnets which are attached to the loadbalancer.
Then the subnet result is used to identify the instance by querying for ports which are attached to the subnets above.
Yet, when the first query result is empty due to deletion, bug or any other reason within the Neutron side, this may cause a security vulnerability, as Neutron will retrieve ports of _any_ instance which has the same IP address as the instance which is queried.
That could compromise key pairs and other sensitive data. |
While querying metadata from an instance via a loadbalancer, metadata service relies on X-Metadata-Provider to identify the correct instance by querying Neutron for subnets which are attached to the loadbalancer.
Then the subnet result is used to identify the instance by querying for ports which are attached to the subnets above.
Yet, when the first query result is empty due to deletion, bug or any other reason within the Neutron side, this may cause a security vulnerability, as Neutron will retrieve ports of _any_ instance which has the same IP address as the instance which is queried.
That could compromise key pairs and other sensitive data. |
|
| 2019-10-31 09:33:28 |
OpenStack Infra |
nova: assignee |
Kobi Samoray (ksamoray) |
Adit Sarfaty (asarfaty) |
|
| 2019-10-31 19:47:04 |
OpenStack Infra |
nova: assignee |
Adit Sarfaty (asarfaty) |
Kobi Samoray (ksamoray) |
|
| 2019-11-05 11:06:30 |
OpenStack Infra |
nova: assignee |
Kobi Samoray (ksamoray) |
Adit Sarfaty (asarfaty) |
|
| 2020-01-28 09:34:50 |
OpenStack Infra |
nova: assignee |
Adit Sarfaty (asarfaty) |
Kobi Samoray (ksamoray) |
|
| 2020-02-04 12:59:25 |
OpenStack Infra |
nova: status |
In Progress |
Fix Released |
|
