Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-47951

Path Traversal in cinder (CVE-2022-47951)

Summary

Path traversal in cinder (CVE-2022-47951). Confidential information can be exposed externally. Mitigation: upgrade to 20.0.2 or later.

Original description

The description as published by the source.

An issue was discovered in OpenStack Cinder before 19.1.2, 20.x before 20.0.2, and 21.0.0; Glance before 23.0.1, 24.x before 24.1.1, and 25.0.0; and Nova before 24.1.2, 25.x before 25.0.2, and 26.0.0. By supplying a specially created VMDK flat image that references a specific backing file path, an authenticated user may convince systems to return a copy of that file's contents from the server, resulting in unauthorized access to potentially sensitive data.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-2022-47951 has been found in cinder.
Confidential information can be exposed externally.
What to do: upgrade cinder to 20.0.2 or later.
If unsure, ask your IT team or search "cinder CVE-2022-47951" on the vendor's site.

CVE-2022-47951 (cinder) — CWE-22
Attack vector: remote (network-reachable)
Patched: 20.0.2 — 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.

❓ What is the problem

Path traversal (CWE-22) exists in cinder.

📍 Affected scope

Check the vendor advisory for the affected versions of cinder.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 20.0.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'cinder' . 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. 1
    Identify exposure identify 
    grep -r 'cinder' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で cinder を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade cinder to 20.0.2

    ステージング環境で 20.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI cinder
[{"type":"ECOSYSTEM","events":[{"introduced":"20.0.0"},{"fixed":"20.0.2"}]}]
PyPI glance
[{"type":"ECOSYSTEM","events":[{"introduced":"24.0.0"},{"fixed":"24.1.1"}]}]
PyPI nova
[{"type":"ECOSYSTEM","events":[{"introduced":"25.0.0"},{"fixed":"25.0.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details