← Back
CVE-2015-3171
medium
CVSS 5.5
Information Disclosure in sosreport (CVE-2015-3171)
Summary
vulnerability in sosreport (CVE-2015-3171). Confidential information can be exposed externally. Mitigation: upgrade to `d7759d3ddae5fe99a340c88a1d370d65cfa73fd6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2015-3171** has been found in sosreport.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade sosreport to **d7759d3ddae5fe99a340c88a1d370d65cfa73fd6** or later.
If unsure, ask your IT team or search "sosreport CVE-2015-3171" on the vendor's site.
CVE-2015-3171 (sosreport) — CWE-200 / CVSS v3 5.5
Attack vector: local / no user interaction
Patched: `d7759d3ddae5fe99a340c88a1d370d65cfa73fd6` — 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
**information disclosure** (CWE-200) exists in sosreport.
📍 Affected scope
sosreport — .
🔥 Severity
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **d7759d3ddae5fe99a340c88a1d370d65cfa73fd6**.
🛡️ 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 'sosreport' .` 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
-
1Identify exposure identify
grep -r 'sosreport' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `sosreport` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade sosreport to d7759d3ddae5fe99a340c88a1d370d65cfa73fd6ステージング環境で d7759d3ddae5fe99a340c88a1d370d65cfa73fd6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
sosreport
[{"repo":"https:\/\/github.com\/sosreport\/sos","type":"GIT","events":[{"introduced":"0"},{"fixed":"d7759d3ddae5fe99a340c88a1d370d65cfa73fd6"}]},{"type":"ECOSYSTEM","events":[{"introduced":"3.0"}]}]