| 2015-06-11 20:01:35 |
Josh Kleinpeter |
bug |
|
|
added bug |
| 2015-06-11 20:13:04 |
Jeremy Stanley |
bug task added |
|
ossa |
|
| 2015-06-11 20:13:10 |
Jeremy Stanley |
ossa: status |
New |
Incomplete |
|
| 2015-06-11 20:13:22 |
Jeremy Stanley |
description |
Keystone tokens that are deleted using the v3 api are still accepted by
the v2 api. Steps to reproduce:
1. Request a scoped token as a member of a tenant.
2. Delete it using DELETE /v3/auth/tokens
3. Request the tenants you can access with GET v2.0/tenants
4. The token is accepted and keystone returns the list of tenants
The token was a PKI token. Admin tokens appear to be deleted correctly.
This could be a problem if a user's access needs to be revoked but they
are still able to access v2 functions. |
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.
Keystone tokens that are deleted using the v3 api are still accepted by
the v2 api. Steps to reproduce:
1. Request a scoped token as a member of a tenant.
2. Delete it using DELETE /v3/auth/tokens
3. Request the tenants you can access with GET v2.0/tenants
4. The token is accepted and keystone returns the list of tenants
The token was a PKI token. Admin tokens appear to be deleted correctly.
This could be a problem if a user's access needs to be revoked but they
are still able to access v2 functions. |
|
| 2015-06-11 20:13:44 |
Jeremy Stanley |
bug |
|
|
added subscriber Keystone Core security contacts |
| 2015-06-11 20:27:14 |
Dolph Mathews |
tags |
|
pki |
|
| 2015-06-11 20:27:20 |
Dolph Mathews |
keystone: importance |
Undecided |
High |
|
| 2015-06-11 22:34:32 |
Dolph Mathews |
attachment added |
|
Test for master https://bugs.launchpad.net/keystone/+bug/1464377/+attachment/4413522/+files/bug-1464377-master.patch |
|
| 2015-06-11 22:34:38 |
Dolph Mathews |
keystone: status |
New |
Incomplete |
|
| 2015-06-12 14:41:37 |
Dolph Mathews |
attachment added |
|
Test for master https://bugs.launchpad.net/keystone/+bug/1464377/+attachment/4413947/+files/bug-1464377-master-v2.patch |
|
| 2015-07-14 16:58:28 |
Grant Murphy |
bug task deleted |
ossa |
|
|
| 2015-07-14 16:58:34 |
Grant Murphy |
information type |
Private Security |
Public |
|
| 2015-08-19 18:21:25 |
Tristan Cacqueray |
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.
Keystone tokens that are deleted using the v3 api are still accepted by
the v2 api. Steps to reproduce:
1. Request a scoped token as a member of a tenant.
2. Delete it using DELETE /v3/auth/tokens
3. Request the tenants you can access with GET v2.0/tenants
4. The token is accepted and keystone returns the list of tenants
The token was a PKI token. Admin tokens appear to be deleted correctly.
This could be a problem if a user's access needs to be revoked but they
are still able to access v2 functions. |
Keystone tokens that are deleted using the v3 api are still accepted by
the v2 api. Steps to reproduce:
1. Request a scoped token as a member of a tenant.
2. Delete it using DELETE /v3/auth/tokens
3. Request the tenants you can access with GET v2.0/tenants
4. The token is accepted and keystone returns the list of tenants
The token was a PKI token. Admin tokens appear to be deleted correctly.
This could be a problem if a user's access needs to be revoked but they
are still able to access v2 functions. |
|
| 2015-10-20 04:17:29 |
Launchpad Janitor |
keystone: status |
Incomplete |
Expired |
|
| 2015-11-10 17:08:45 |
OpenStack Infra |
tags |
pki |
in-stable-juno pki |
|
| 2015-11-14 10:33:33 |
Alan Pevec |
nominated for series |
|
keystone/juno |
|
| 2015-11-14 10:33:34 |
Alan Pevec |
bug task added |
|
keystone/juno |
|
| 2015-11-14 15:06:20 |
Alan Pevec |
keystone/juno: status |
New |
Fix Committed |
|
| 2015-11-14 15:06:20 |
Alan Pevec |
keystone/juno: milestone |
|
2014.2.4 |
|
| 2015-11-19 21:43:21 |
Alan Pevec |
keystone/juno: status |
Fix Committed |
Fix Released |
|
| 2015-11-26 05:53:54 |
OpenStack Infra |
tags |
in-stable-juno pki |
in-stable-juno in-stable-kilo pki |
|
| 2016-01-21 20:25:21 |
Dave Walker |
nominated for series |
|
keystone/kilo |
|
| 2016-01-21 20:25:21 |
Dave Walker |
bug task added |
|
keystone/kilo |
|
| 2016-01-21 20:26:09 |
Dave Walker |
keystone/kilo: status |
New |
Fix Committed |
|
| 2016-01-21 20:26:09 |
Dave Walker |
keystone/kilo: milestone |
|
2015.1.3 |
|
| 2016-01-21 23:16:49 |
Dave Walker |
keystone/kilo: status |
Fix Committed |
Fix Released |
|
