A vulnerability was found in Keystone's OAuth1 Token API. Previously the list of roles provided for an OAuth1 access token were ignored, so when an access token was used to request a keystone token, the keystone token would contain 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.
Created attachment 1683827 [details] propossed patch
Created attachment 1683828 [details] propossed patch
Created attachment 1683829 [details] propossed patch
References: https://launchpad.net/bugs/1873290
Created openstack-keystone tracking bugs for this issue: Affects: openstack-rdo [bug 1832400]
External References: https://security.openstack.org/ossa/OSSA-2020-005.html
Acknowledgments: Name: kay (OpenStack)
*** Bug 1850063 has been marked as a duplicate of this bug. ***
This issue has been addressed in the following products: Red Hat OpenStack Platform 15.0 (Stein) Via RHSA-2020:3102 https://access.redhat.com/errata/RHSA-2020:3102
This issue has been addressed in the following products: Red Hat OpenStack Platform 16.0 (Train) Via RHSA-2020:3105 https://access.redhat.com/errata/RHSA-2020:3105
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2020-12690
Statement: Red Hat Quay includes keystone-client, which is not vulnerable to this (server-side) vulnerability.