Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2020-10755

Vulnerability in cinder (CVE-2020-10755)

Summary

vulnerability in cinder (CVE-2020-10755). Confidential information can be exposed externally. Exploitable via ``connection_info``. Mitigation: upgrade to `14.1.0, 15.2.0, 16.1.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2020-10755** has been found in cinder. Attackers can target a specific entry point like ``connection_info`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade cinder to **14.1.0, 15.2.0, 16.1.0** or later. If unsure, ask your IT team or search "cinder CVE-2020-10755" on the vendor's site.
CVE-2020-10755 (cinder) — CWE-522 / Attack vector: remote (network-reachable) / no user interaction Attack surface: `connection_info` Patched: `14.1.0, 15.2.0, 16.1.0` — 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
**A vulnerability** (CWE-522) exists in cinder. Attackers reach the vulnerable code path via ``connection_info`` without authentication.
📍 Affected scope
cinder — . Attack surface: `connection_info`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **14.1.0, 15.2.0, 16.1.0**.
🛡️ 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 (7 steps)

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. 6
    Apply patch patch 
    Upgrade cinder to 14.1.0, 15.2.0, 16.1.0

    ステージング環境で 14.1.0, 15.2.0, 16.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

PyPI cinder
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.1.0"},{"introduced":"15.0.0"},{"fixed":"15.2.0"},{"introduced":"16.0.0"},{"fixed":"16.1.0"}]}]
PyPI os-brick
[{"type":"ECOSYSTEM","events":[{"introduced":"2.8.0"},{"fixed":"2.8.6"},{"introduced":"2.10.0"},{"fixed":"2.10.4"},{"introduced":"3.0.0"},{"fixed":"3.0.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →