← Back

Keystone

keystone

Vendor: Openstack • 44 CVEs

CVEs (44)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
CVE-2012-4457
1Openstack
1Keystone
Apr 29, 2026
Oct 9, 2012
N/A· v4
N/A· v3
4.0 MEDIUM· v2
OpenStack Keystone Essex before 2012.1.2 and Folsom before folsom-3 does not properly handle authorization tokens for disabled tenants, which allows remote authenticated users to access the tenant's resources by requesti...Show more
OpenStack Keystone Essex before 2012.1.2 and Folsom before folsom-3 does not properly handle authorization tokens for disabled tenants, which allows remote authenticated users to access the tenant's resources by requesting a token for the tenant.Show less
CVE-2012-4456
1Openstack
1Keystone
Apr 29, 2026
Oct 9, 2012
N/A· v4
N/A· v3
7.5 HIGH· v2
The (1) OS-KSADM/services and (2) tenant APIs in OpenStack Keystone Essex before 2012.1.2 and Folsom before folsom-2 do not properly validate X-Auth-Token, which allow remote attackers to read the roles for an arbitrary...Show more
The (1) OS-KSADM/services and (2) tenant APIs in OpenStack Keystone Essex before 2012.1.2 and Folsom before folsom-2 do not properly validate X-Auth-Token, which allow remote attackers to read the roles for an arbitrary user or get, create, or delete arbitrary services.Show less
CVE-2012-4413
1Openstack
1Keystone
Apr 29, 2026
Sep 18, 2012
N/A· v4
N/A· v3
4.0 MEDIUM· v2
OpenStack Keystone 2012.1.3 does not invalidate existing tokens when granting or revoking roles, which allows remote authenticated users to retain the privileges of the revoked roles.
CVE-2012-3426
1Openstack
3Essex
HorizonKeystone
Apr 29, 2026
Jul 31, 2012
N/A· v4
N/A· v3
4.9 MEDIUM· v2
OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization...Show more
OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.Show less