| 2016-02-15 13:21:52 |
Stuart McLaren |
bug |
|
|
added bug |
| 2016-02-15 15:06:44 |
Tristan Cacqueray |
bug task added |
|
ossa |
|
| 2016-02-15 15:06:51 |
Tristan Cacqueray |
ossa: status |
New |
Incomplete |
|
| 2016-02-15 15:08:17 |
Tristan Cacqueray |
description |
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
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.
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
|
| 2016-02-15 15:08:43 |
Tristan Cacqueray |
bug |
|
|
added subscriber Glance Core security contacts |
| 2016-02-15 15:15:47 |
Stuart McLaren |
bug |
|
|
added subscriber Travis Tripp |
| 2016-02-18 04:07:32 |
Flavio Percoco |
bug |
|
|
added subscriber Lakshmi N Sampath |
| 2016-03-29 18:16:03 |
Tristan Cacqueray |
bug |
|
|
added subscriber OSSG CoreSec |
| 2016-05-16 16:36:28 |
Tristan Cacqueray |
ossa: status |
Incomplete |
Opinion |
|
| 2020-02-27 22:50:38 |
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.
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
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. This
embargo shall not extend past 2020-05-27 and will be made
public by or on that date if no fix is identified.
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
|
| 2020-02-28 15:30:20 |
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. This
embargo shall not extend past 2020-05-27 and will be made
public by or on that date if no fix is identified.
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
|
| 2020-02-28 15:31:17 |
Jeremy Stanley |
description |
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
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. This
embargo shall not extend past 2020-05-27 and will be made
public by or on that date if no fix is identified.
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
|
| 2020-05-27 16:55:58 |
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. This
embargo shall not extend past 2020-05-27 and will be made
public by or on that date if no fix is identified.
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
User 1 can create a new namespace with visibility 'public':
$ cat /tmp/ns.json
{"namespace": "NS1001", "visibility": "public"}
$ curl -X POST http://localhost:9292/v2/metadefs/namespaces -H 'x-auth-token: cb334b03257144049b29cd8859b8a3bd' -H 'Content-Type: application/json' -d@/tmp/ns.json
The new namespace shows up in other users' namespace listing:
$ glance md-namespace-list
+------------------------------------------+
| namespace |
+------------------------------------------+
| NS1001 |
| OS::Compute::GuestMemoryBacking |
| OS::Compute::VMware |
| OS::Compute::LibvirtImage |
| OS::Compute::AggregateIoOpsFilter |
| OS::Compute::Hypervisor |
| OS::Compute::VirtCPUTopology |
| OS::Compute::RandomNumberGenerator |
This allows a regular user to spam all other users' namespace listing. |
|
| 2020-05-27 16:56:05 |
Jeremy Stanley |
information type |
Private Security |
Public Security |
|
| 2020-05-27 16:57:10 |
Jeremy Stanley |
information type |
Public Security |
Public |
|
