p PatchFirst

PatchFirst · Latest vulnerabilities

keystone vulnerabilities · Page 2

Vulnerabilities published for keystone in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 56

  1. CVE-2018-14432

    Medium · CVSS 5.3EPSS 1.6%Fix available

    CVE-2018-14432

    In the Federation component of OpenStack Keystone before 11.0.4, 12.0.0, and 13.0.0, an authenticated "GET /v3/OS-FEDERATION/projects" request may bypass intended access restrictions on listing projects. An authenticated user may discover projects they have no authority to access, leaking all projects in the deployment and their attributes. Only Keystone with the /v3/OS-FEDERATION endpoint enabled via policy.json is affected.

    • Update to 2:13.0.0-7
    Published Updated
  2. CVE-2015-7546

    High · CVSS 7.5EPSS 2%Fix available

    CVE-2015-7546

    The identity service in OpenStack Identity (Keystone) before 2015.1.3 (Kilo) and 8.0.x before 8.0.2 (Liberty) and keystonemiddleware (formerly python-keystoneclient) before 1.5.4 (Kilo) and Liberty before 2.3.3 does not properly invalidate authorization tokens when using the PKI or PKIZ token providers, which allows remote authenticated users to bypass intended access restrictions and gain access to cloud resources by manipulating byte fields within a revoked token.

    • Update to 2:9.0.0~rc2-1
    Published Updated
  3. CVE-2014-5252

    Medium · CVSS 6.5EPSS 1.52%Fix available

    CVE-2014-5252

    The V3 API in OpenStack Identity (Keystone) 2014.1.x before 2014.1.2.1 and Juno before Juno-3 updates the issued_at value for UUID v2 tokens, which allows remote authenticated users to bypass the token expiration and retain access via a verification (1) GET or (2) HEAD request to v3/auth/tokens/.

    • Update to 2014.1.2.1-1
    Published Updated
  4. CVE-2014-5251

    Medium · CVSS 6.5EPSS 1.59%Fix available

    CVE-2014-5251

    The MySQL token driver in OpenStack Identity (Keystone) 2014.1.x before 2014.1.2.1 and Juno before Juno-3 stores timestamps with the incorrect precision, which causes the expiration comparison for tokens to fail and allows remote authenticated users to retain access via an expired token.

    • Update to 2014.1.2.1-1
    Published Updated
  5. CVE-2014-3476

    Not ratedEPSS 2.33%Fix available

    CVE-2014-3476

    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.

    • Update to 2014.1.1-2
    Published Updated
  6. CVE-2014-0105

    Medium · CVSS 6EPSS 1.1%Fix available

    CVE-2014-0105

    The auth_token middleware in the OpenStack Python client library for Keystone (aka python-keystoneclient) before 0.7.0 does not properly retrieve user tokens from memcache, which allows remote authenticated users to gain privileges in opportunistic circumstances via a large number of requests, related to an "interaction between eventlet and python-memcached."

    • Update to 2013.1.1-2
    Published Updated
  7. CVE-2014-2237

    Medium · CVSS 6.5EPSS 1.37%Fix available

    CVE-2014-2237

    The memcache token backend in OpenStack Identity (Keystone) 2013.1 through 2.013.1.4, 2013.2 through 2013.2.2, and icehouse before icehouse-3, when issuing a trust token with impersonation enabled, does not include this token in the trustee's token-index-list, which prevents the token from being invalidated by bulk token revocation and allows the trustee to bypass intended access restrictions.

    • Update to 2013.2.3-1
    Published Updated
  8. CVE-2013-6391

    Not ratedEPSS 2.24%Fix available

    CVE-2013-6391

    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.

    • Update to 2013.2.1-1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →