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-2018-20170 has been found in keystone.
Attackers can target a specific entry point like POST /v3/auth/tokens over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "keystone UBUNTU-CVE-2018-20170" on the vendor's site.
UBUNTU-CVE-2018-20170 (keystone)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /v3/auth/tokens
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. Attackers reach the vulnerable code path via POST /v3/auth/tokens without authentication.
Check the vendor advisory for the affected versions of keystone. Attack surface: POST /v3/auth/tokens.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /v3/auth/tokens requests with malformed payloads or SQL meta-characters. 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
Hunt for indicators of compromisedetect
grep 'POST /v3/auth/tokens' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /v3/auth/tokensへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3
Post-deployment verificationverify
Replay attack against POST /v3/auth/tokens on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Ubuntu:Pro:16.04:LTS | keystone |
All versions |
— |
| Ubuntu:Pro:18.04:LTS | keystone |
All versions |
— |
Original description The description as published by the source.
OpenStack Keystone through 14.0.1 has a user enumeration vulnerability because invalid usernames have much faster responses than valid ones for a POST /v3/auth/tokens request. NOTE: the vendor's position is that this is a hardening opportunity, and not necessarily an issue that should have an OpenStack Security Advisory
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- report ubuntu.com
- report bugs.launchpad.net
- report cve.org