| 2017-04-28 13:11:09 |
György Szombathelyi |
bug |
|
|
added bug |
| 2017-04-28 14:46:24 |
Jeremy Stanley |
description |
During working on bug #1686616, I realized that using the privileged user to find the host for an instance works for any other projects, even if the requesting user doesn't have rights to see other projects' instances.
I guess it is not a big impact, one has to know an UUID of a foreign instance, and the maximum effect is to put a volume on the host where the instance resides (if it has a cinder-volume running).
I think after the filter gets the server info via the privileged user, it must check if it has rights to access that info. If a privileged user is not configured, there's no problem. |
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.
During working on bug #1686616, I realized that using the privileged user to find the host for an instance works for any other projects, even if the requesting user doesn't have rights to see other projects' instances.
I guess it is not a big impact, one has to know an UUID of a foreign instance, and the maximum effect is to put a volume on the host where the instance resides (if it has a cinder-volume running).
I think after the filter gets the server info via the privileged user, it must check if it has rights to access that info. If a privileged user is not configured, there's no problem. |
|
| 2017-04-28 14:46:33 |
Jeremy Stanley |
bug task added |
|
ossa |
|
| 2017-04-28 14:46:52 |
Jeremy Stanley |
ossa: status |
New |
Incomplete |
|
| 2017-04-28 14:47:10 |
Jeremy Stanley |
bug |
|
|
added subscriber Cinder Core security contacts |
| 2017-04-28 14:50:54 |
Jeremy Stanley |
bug |
|
|
added subscriber OSSG CoreSec |
| 2017-05-24 14:38:56 |
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.
During working on bug #1686616, I realized that using the privileged user to find the host for an instance works for any other projects, even if the requesting user doesn't have rights to see other projects' instances.
I guess it is not a big impact, one has to know an UUID of a foreign instance, and the maximum effect is to put a volume on the host where the instance resides (if it has a cinder-volume running).
I think after the filter gets the server info via the privileged user, it must check if it has rights to access that info. If a privileged user is not configured, there's no problem. |
During working on bug #1686616, I realized that using the privileged user to find the host for an instance works for any other projects, even if the requesting user doesn't have rights to see other projects' instances.
I guess it is not a big impact, one has to know an UUID of a foreign instance, and the maximum effect is to put a volume on the host where the instance resides (if it has a cinder-volume running).
I think after the filter gets the server info via the privileged user, it must check if it has rights to access that info. If a privileged user is not configured, there's no problem. |
|
| 2017-05-24 14:39:02 |
Jeremy Stanley |
information type |
Private Security |
Public |
|
| 2017-05-24 14:39:11 |
Jeremy Stanley |
tags |
|
security |
|
| 2017-05-24 14:39:15 |
Jeremy Stanley |
ossa: status |
Incomplete |
Won't Fix |
|
