Vulnerability in keystone
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2020-12690 has been found in keystone.
Successful exploitation can lead to full system takeover.
What to do: upgrade keystone to 2:13.0.4-0ubuntu1 or later.
If unsure, ask your IT team or search "keystone UBUNTU-CVE-2020-12690" on the vendor's site.
UBUNTU-CVE-2020-12690 (keystone)
Attack vector: remote (network-reachable) / no user interaction
Patched: 2:13.0.4-0ubuntu1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in keystone.
Check the vendor advisory for the affected versions of keystone.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2:13.0.4-0ubuntu1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'keystone' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'keystone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
keystoneを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade keystone to 2:13.0.4-0ubuntu1ステージング環境で 2:13.0.4-0ubuntu1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Ubuntu:Pro:16.04:LTS | keystone |
All versions |
— |
| Ubuntu:18.04:LTS | keystone |
< 2:13.0.4-0ubuntu1 |
2:13.0.4-0ubuntu1 |
Original description The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory ubuntu.com
- report ubuntu.com
- report openwall.com
- report cve.org