Insufficient Session Expiration in OpenStack KeystoneGHSA-6m8p-x4qw-gh5j
HIGHGHSA-6m8p-x4qw-gh5j is a high-severity (CVSS 8.8) CWE-613 vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-6m8p-x4qw-gh5j by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
keystone🐍keystoneReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | keystone | all versions | 15.0.1pip install --upgrade 'keystone==15.0.1' |
| 🐍PyPI | keystone | ≥ 16.0.0.0rc1&&< 16.0.0 | 16.0.0pip install --upgrade 'keystone==16.0.0' |
Affected Products
keystoneopenstackDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keystone to 15.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6m8p-x4qw-gh5j is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Quay includes keystone-client, which is not vulnerable to this (server-side) vulnerability.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 15.0 (Stein) | openstack-keystone-1:15.0.1-0.20200512110437.95b2bbe.el8ost | RHSA-2020:3102 |
| Red Hat OpenStack Platform 16.0 (Train) | openstack-keystone-1:16.0.1-0.20200511063421.40cbb7b.el8ost | RHSA-2020:3105 |
Frequently Asked Questions
Is GHSA-6m8p-x4qw-gh5j in your dependencies?
Find it across PyPI, including transitive dependencies.