Описание
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 used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access.
A flaw was found in Keystone, where it inadvertently provided OAuth1 access tokens to every role assignment the creator had for a project, resulting in giving more permissions and escalated access in role assignments than intended. The greatest impact is on confidentiality.
Отчет
Red Hat Quay includes keystone-client, which is not vulnerable to this (server-side) vulnerability.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) | openstack-keystone | Out of support scope | ||
| Red Hat JBoss Fuse 6 | openstack-keystone | Not affected | ||
| Red Hat OpenStack Platform 10 (Newton) | openstack-keystone | Affected | ||
| Red Hat OpenStack Platform 13 (Queens) | openstack-keystone | Affected | ||
| Red Hat Quay 3 | quay/quay-rhel8 | Not affected | ||
| Red Hat OpenStack Platform 15.0 (Stein) | openstack-keystone | Fixed | RHSA-2020:3102 | 22.07.2020 |
| Red Hat OpenStack Platform 16.0 (Train) | openstack-keystone | Fixed | RHSA-2020:3105 | 22.07.2020 |
Показывать по
Дополнительная информация
Статус:
8.8 High
CVSS3
Связанные уязвимости
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 used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access.
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 used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access.
An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0. ...
Insufficient Session Expiration in OpenStack Keystone
8.8 High
CVSS3