GHSA-8c4w-v65p-jvcv
HIGHGHSA-8c4w-v65p-jvcv is a high-severity (CVSS 7.5) CWE-522 vulnerability in keystone. O3 Security confirms whether GHSA-8c4w-v65p-jvcv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenStack Identity Keystone and keystonemiddleware Insufficiently Protected Credentials
Blast Radius
keystone🐍keystonemiddleware🐍keystone🐍keystonemiddleware🐍keystonemiddlewareReal-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
The identity service in OpenStack Identity (Keystone) before 2015.1.3 (Kilo) and 8.0.x before 8.0.2 (Liberty) and keystonemiddleware (formerly python-keystoneclient) before 1.5.4 (Kilo) and Liberty before 2.3.3 does not properly invalidate authorization tokens when using the PKI or PKIZ token providers, which allows remote authenticated users to bypass intended access restrictions and gain access to cloud resources by manipulating byte fields within a revoked token.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | keystone | ≥ 9.0.0.0b1&&< 9.0.0.0b2 | 9.0.0.0b2 |
| 🐍PyPI | keystonemiddleware | ≥ 2.4.0&&< 4.1.0 | 4.1.0 |
| 🐍PyPI | keystone | ≥ 8.0&&< 8.1.0 | 8.1.0 |
| 🐍PyPI | keystonemiddleware | all versions | 1.5.4 |
| 🐍PyPI | keystonemiddleware | ≥ 1.6.0&&< 2.3.3 | 2.3.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update keystone to 9.0.0.0b2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c4w-v65p-jvcv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8c4w-v65p-jvcv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-8c4w-v65p-jvcv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8c4w-v65p-jvcv in your dependencies?
O3 detects GHSA-8c4w-v65p-jvcv across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.