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.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2014:0089 advisory.

    The openstack-keystone packages provide keystone, a Python implementation     of the OpenStack Identity service API, which provides Identity, Token,     Catalog, and Policy services.

    It was found that the ec2token API in keystone, which is used to generate     EC2-style (Amazon Elastic Compute Cloud) credentials, could generate a     token not scoped to a particular trust when creating a token from a     received trust-scoped token. A remote attacker could use this flaw to     retrieve a token that elevated their privileges to all of the trustor's     roles. Note that only OpenStack Identity setups that have EC2-style     authentication enabled were affected. (CVE-2013-6391)

    Red Hat would like to thank Jeremy Stanley of the OpenStack Project for     reporting this issue. Upstream acknowledges Steven Hardy of Red Hat as the     original reporter.

    These updated packages have been upgraded to upstream version 2013.2.1,     which provides a number of bug fixes over the previous version.
    (BZ#1045408)

    All openstack-keystone users are advised to upgrade to these updated     packages, which correct these issues.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2014:0368 advisory.

    The OpenStack Identity service (keystone) authenticates and authorizes     OpenStack users by keeping track of users and their permitted activities.
    The Identity service supports multiple forms of authentication including     user name and password credentials, token-based systems, and     AWS-style logins.

    It was found that the ec2token API in keystone, which is used to generate     EC2-style (Amazon Elastic Compute Cloud) credentials, could generate a     token not scoped to a particular trust when creating a token from a     received trust-scoped token. A remote attacker could use this flaw to     retrieve a token that elevated their privileges to all of the trustor's     roles. Note that only OpenStack Identity setups that have EC2-style     authentication enabled were affected. (CVE-2013-6391)

    It was found that the the memcache token back end of OpenStack Identity did     not correctly invalidate a revoked trust token, allowing users with revoked     tokens to retain access to services they should no longer be able to     access. Note that only OpenStack Identity setups using the memcache back     end for tokens were affected. (CVE-2014-2237)

    Red Hat would like to thank Jeremy Stanley of the OpenStack Project for     reporting CVE-2013-6391. Upstream acknowledges Steven Hardy of Red Hat as     the original reporter of CVE-2013-6391.

    All openstack-keystone users are advised to upgrade to these updated     packages, which correct these issues.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

updated to stable grizzly 2013.1.5 release

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Steven Hardy discovered that Keystone did not properly enforce trusts when using the ec2tokens API. An authenticated attacker could exploit this to retrieve a token not scoped to the trust and elevate privileges to the trustor's roles.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
210159	RHEL 6 : openstack-keystone (RHSA-2014:0089)	Nessus	Red Hat Local Security Checks	critical
193836	RHEL 6 : openstack-keystone (RHSA-2014:0368)	Nessus	Red Hat Local Security Checks	critical
73353	Fedora 19 : openstack-keystone-2013.1.5-2.fc19 (2014-4210)	Nessus	Fedora Local Security Checks	medium
71564	Ubuntu 13.10 : keystone vulnerability (USN-2061-1)	Nessus	Ubuntu Local Security Checks	medium

Detections

Analytics

CVE-2013-6391

critical

Tenable Plugins

critical

critical

medium

medium