OpenStack Identity (Keystone) before 2013.2.4, 2014.1 before 2014.1.2, and Juno before Juno-2 does not properly handle chained delegation, which allows remote authenticated users to gain privileges by leveraging a (1) trust or (2) OAuth token with impersonation enabled to create a new token with additional roles.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2014:0994 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.

    A flaw was found in keystone's chained delegation. A trustee able to create     a delegation from a trust or an OAuth token could misuse identity     impersonation to bypass the enforced scope, possibly allowing them to     obtain elevated privileges to the trustor's projects and roles.
    (CVE-2014-3476)

    A flaw was found in the way keystone handled trusts. A trustee could use an     out-of-scope project ID to gain unauthorized access to a project if the     trustor had the required roles for that requested project. (CVE-2014-3520)

    Red Hat would like to thank the OpenStack project for reporting     CVE-2014-3520; upstream acknowledges Jamie Lennox of Red Hat as the     original reporter. The CVE-2014-3476 issue was discovered by Steven Hardy     of Red Hat.

    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.

The remote Ubuntu 14.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-2324-1 advisory.

    Steven Hardy discovered that OpenStack Keystone did not properly handle chained delegation. A remove     authenticated attacker could use this to gain privileges by creating a new token with additional roles.
    (CVE-2014-3476)

    Jamie Lennox discovered that OpenStack Keystone did not properly validate the project id. A remote     authenticated attacker may be able to use this to access other projects. (CVE-2014-3520)

    Brant Knudson and Lance Bragstad discovered that OpenStack Keystone would not always revoke tokens     correctly. If Keystone were configured to use revocation events, a remote authenticated attacker could     continue to have access to resources. (CVE-2014-5251, CVE-2014-5252, CVE-2014-5253)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

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

- Sanitizes authentication methods received in requests     CVE-2014-2828

    - Privilege escalation through trust chained delegation       CVE-2014-3476

    - Keystone V2 trusts privilege escalation through user       supplied project id CVE-2014-3520

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.

ID	Name	Product	Family	Severity
210147	RHEL 6 : openstack-keystone (RHSA-2014:0994)	Nessus	Red Hat Local Security Checks	high
77324	Ubuntu 14.04 LTS : OpenStack Keystone vulnerabilities (USN-2324-1)	Nessus	Ubuntu Local Security Checks	high
77061	Fedora 20 : openstack-keystone-2013.2.3-5.fc20 (2014-5497)	Nessus	Fedora Local Security Checks	high

Detections

Analytics

CVE-2014-3476

high

Tenable Plugins

high

high

high