Keystone

Every one of the 45 is a mark on the map. Named now: 1 to 26, most at risk first.

1. An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any authenticated user can create an EC2 credential for themselves for a project that they have a specifie…CVE-2020-12691Openstack · 4.9% likely

   CWE-863

2. 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 atta…CVE-2012-4456Openstack · 4.0% likely

   CWE-287

3. OpenStack Identity (Keystone) before 2013.1 allows remote attackers to cause a denial of service (memory consumption and crash) via multiple long requests.CVE-2013-2014Openstack · 3.3% likely

   CWE-20

4. OpenStack Keystone Essex 2012.1.3 and earlier, Folsom 2012.2.3 and earlier, and Grizzly grizzly-2 and earlier allows remote attackers to cause a denial of service (disk consumptio…CVE-2013-0247Openstack · 3.2% likely

   CWE-399

5. The V3 API in OpenStack Identity (Keystone) 2013.1 before 2013.2.4 and icehouse before icehouse-rc2 allows remote attackers to cause a denial of service (CPU consumption) via a la…CVE-2014-2828Openstack · 3.2% likely

   CWE-287

6. OpenStack Keystone Folsom, Grizzly before 2013.1.3, and Havana, when using LDAP with Anonymous binding, allows remote attackers to bypass authentication via an empty password.CVE-2013-2157Openstack · 3.1% likely

   CWE-287

7. OpenStack Identity (Keystone) before 2014.1.5 and 2014.2.x before 2014.2.4 logs the backend_argument configuration option content, which allows remote authenticated users to obtai…CVE-2015-3646Openstack · 2.9% likely

   CWE-200

8. The (1) mamcache and (2) KVS token backends in OpenStack Identity (Keystone) Folsom 2012.2.x and Grizzly before 2013.1.4 do not properly compare the PKI token revocation list with…CVE-2013-4294Openstack · 2.7% likely

   CWE-264

9. OpenStack Keystone 10.x through 16.x before 16.0.2, 17.x before 17.0.1, 18.x before 18.0.1, and 19.x before 19.0.1 allows information disclosure during account locking (related to…CVE-2021-38155Openstack · 2.5% likely

   CWE-307

10. OpenStack Identity (Keystone) Folsom 2012.2.4 and earlier, Grizzly before 2013.1.1, and Havana does not immediately revoke the authentication token when deleting a user through th…CVE-2013-2059Openstack · 2.5% likely

    CWE-287

11. 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…CVE-2014-3476Openstack · 2.3% likely

    CWE-269

12. 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…CVE-2012-4457Openstack · 2.3% likely

    CWE-287

13. 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 re…CVE-2013-6391Openstack · 2.2% likely

    CWE-269

14. The catalog url replacement in OpenStack Identity (Keystone) before 2013.2.3 and 2014.1 before 2014.1.2.1 allows remote authenticated users to read sensitive configuration options…CVE-2014-3621Openstack · 2.1% likely

    CWE-200

15. A flaw was found in openstack-keystone. Only the first 72 characters of an application secret are verified allowing attackers bypass some password complexity which administrators…CVE-2021-3563Openstack · 2.0% likely

    CWE-863

16. OpenStack Identity (Keystone) before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2 allows remote authenticated trustees to gain access to an unauthorized project for wh…CVE-2014-3520Openstack · 1.9% likely

    CWE-863

17. 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 ro…CVE-2012-4413Openstack · 1.9% likely

    CWE-264

18. An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The list of roles provided for an OAuth1 access token is silently ignored. Thus, when an access token is u…CVE-2020-12690Openstack · 1.9% likely

    CWE-613

19. OpenStack Identity (Keystone) Folsom, Grizzly 2013.1.3 and earlier, and Havana before havana-3 does not properly revoke user tokens when a tenant is disabled, which allows remote…CVE-2013-4222Openstack · 1.9% likely

    CWE-522

20. OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in the list credentials API. Any user with a role on a project is able to list any credentials with the /v3/creden…CVE-2019-19687Openstack · 1.8% likely

    CWE-522

21. OpenStack Keystone Grizzly before 2013.1, Folsom 2012.1.3 and earlier, and Essex does not properly check if the (1) user, (2) tenant, or (3) domain is enabled when using EC2-style…CVE-2013-0282Openstack · 1.8% likely

    CWE-287

22. 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 restricti…CVE-2018-14432Openstack · 1.6% likely

    CWE-200

23. 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 expirati…CVE-2014-5251Openstack · 1.6% likely

    CWE-255

24. An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any user authenticated within a limited scope (trust/oauth/application credential) can create an EC2 crede…CVE-2020-12689Openstack · 1.6% likely

    CWE-269

25. 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 use…CVE-2014-5252Openstack · 1.5% likely

    CWE-255

26. OpenStack Identity (Keystone) 2014.1.x before 2014.1.2.1 and Juno before Juno-3 does not properly revoke tokens when a domain is invalidated, which allows remote authenticated use…CVE-2014-5253Openstack · 1.5% likely

    CWE-255

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.