Buffer Overflow in keystone (CVE-2013-0270)
Summary
Vulnerability in keystone (CVE-2013-0270). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.0.0a0 or later.
Original description
The description as published by the source.
OpenStack Keystone Grizzly before 2013.1, Folsom, and possibly earlier allows remote attackers to cause a denial of service (CPU and memory consumption) via a large HTTP request, as demonstrated by a long tenant_name when requesting a token.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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 CVE-2013-0270 has been found in keystone.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade keystone to 8.0.0a0 or later.
If unsure, ask your IT team or search "keystone CVE-2013-0270" on the vendor's site.
CVE-2013-0270 (keystone) — CWE-119 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 8.0.0a0 — 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 (CWE-119) exists in keystone.
Check the vendor advisory for the affected versions of keystone.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 8.0.0a0.
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
-
1Identify exposure identify
grep -r 'keystone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
keystoneを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade keystone to 8.0.0a0ステージング環境で 8.0.0a0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2013-0270 keystone Fixed in: 2013.1.1-2
References
- advisory rhn.redhat.com
- advisory bugs.launchpad.net
- advisory bugzilla.redhat.com
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package pypi.org
- patch launchpad.net
- web secalert@redhat.com
- web access.redhat.com