Keystone: trust circumvention through EC2-style tokens
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 |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenStack 3 for RHEL 6 | |||
| openstack-keystone-0:2013.1.5-2.el6ost | cpe:/a:redhat:openstack:3::el6 | RHSA-2014:0368 | 2014-04-03T00:00:00Z |
| OpenStack 4 for RHEL 6 | |||
| openstack-keystone-0:2013.2.1-1.el6ost | cpe:/a:redhat:openstack:4::el6 | RHSA-2014:0089 | 2014-01-22T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2013-6215 | The ec2tokens API in OpenStack Identity (Keystone) before Havana 2013.2.1 and Icehouse before icehouse-2 does not return a trust-scoped token when one is received, which allows remote trust users to gain privileges by generating EC2 credentials from a trust-scoped token and using them in an ec2tokens API request. |
Ubuntu USN |
USN-2061-1 | OpenStack Keystone vulnerability |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.2% (2.239% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.