CVE-2013-6391 json
The ec2tokens API in OpenStack Identity (Keystone) before Havana 2013.2.1 and Icehouse before icehouse-2 does not return a trust-scoped tok…
published 12y ago modified 4mo ago also EUVD-2013-6215
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- openstack keystone 2013.2.1
- keystone Debian 14, Debian 13, Debian 12 2013.2.1-1
debian advisories DEBIAN-CVE-2013-6391
- openstack-keystone openstack 3 2013.1.5-2.el6ost
- python-keystone openstack 3 2013.1.5-2.el6ost
- openstack-keystone openstack 4 2013.2.1-1.el6ost
- python-keystone openstack 4 2013.2.1-1.el6ost
red hat advisories RHSA-2014:0368RHSA-2014:0089
Is CVE-2013-6391 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-6391 updated cvss 4.0
Keystone: trust circumvention through EC2-style tokens
-
Red Hat Enterprise Linux OpenStack Platform 3.0 python-keystone 2013.1.5-2.el6ost, openstack-keystone 2013.1.5-2.el6ostfixed: vendor fix RHSA-2014:0368
-
Red Hat Enterprise Linux OpenStack Platform 4.0 python-keystone 2013.2.1-1.el6ost, openstack-keystone 2013.2.1-1.el6ostfixed: vendor fix RHSA-2014:0089
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.24% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugs.launchpad.net https://bugs.launchpad.net/keystone/+bug/1242597 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
bugs.launchpad.net
/keystone/+bug/1242597
exploit, issue-tracking, third-party-advisory
-
ubuntu.com
/usn/USN-2061-1
vendor-advisory, third-party-advisory
-
rhn.redhat.com
/errata/RHSA-2014-0089.html
vendor-advisory, third-party-advisory
-
securityfocus.com
/bid/64253
vdb-entry, third-party-advisory
-
openwall.com
/lists/oss-security/2013/12/11/7
mailing-list, third-party-advisory
-
secunia.com
/advisories/56154
third-party-advisory
-
secunia.com
/advisories/56079
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/89657
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2013-6391
- NVD CVE-2013-6391
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.