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.
Original description
The description as published by the source.
sosreport 3.2 uses weak permissions for generated sosreport archives, which allows local users with access to /var/tmp/ to obtain sensitive information by reading the contents of the archive.
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-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.
Information disclosure (CWE-200) exists in sosreport.
Check the vendor advisory for the affected versions of sosreport.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to d7759d3ddae5fe99a340c88a1d370d65cfa73fd6.
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 'sosreport' . 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 'sosreport' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sosreportを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sosreport to d7759d3ddae5fe99a340c88a1d370d65cfa73fd6ステージング環境で d7759d3ddae5fe99a340c88a1d370d65cfa73fd6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-2015-3171 sosreport Fixed in: 3.2-2
References
- advisory github.com
- patch github.com
- report bugzilla.redhat.com