Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2015-6941 critical CVSS 9.8

Vulnerability in salt (CVE-2015-6941)

Summary

Vulnerability in salt (CVE-2015-6941). Successful exploitation can lead to full system takeover. Mitigation: upgrade to c0689e32154c41f59840ae10ffc5fbfa30618710, 2015.5.6, 2015.8.1 or later.

Original description

The description as published by the source.

win_useradd, salt-cloud and the Linode driver in salt 2015.5.x before 2015.5.6, and 2015.8.x before 2015.8.1 leak password information in debug logs.

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-6941 has been found in salt.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade salt to c0689e32154c41f59840ae10ffc5fbfa30618710, 2015.5.6, 2015.8.1 or later.
If unsure, ask your IT team or search "salt CVE-2015-6941" on the vendor's site.

CVE-2015-6941 (salt) — CWE-534 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: c0689e32154c41f59840ae10ffc5fbfa30618710, 2015.5.6, 2015.8.1 — 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-534) exists in salt.

📍 Affected scope

Check the vendor advisory for the affected versions of salt.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to c0689e32154c41f59840ae10ffc5fbfa30618710, 2015.5.6, 2015.8.1.

🛡️ 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 'salt' . 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 'salt' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade salt to c0689e32154c41f59840ae10ffc5fbfa30618710, 2015.5.6, 2015.8.1

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

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

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

Affected packages

PyPI salt
[{"repo":"https:\/\/github.com\/twangboy\/salt","type":"GIT","events":[{"introduced":"0"},{"fixed":"c0689e32154c41f59840ae10ffc5fbfa30618710"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2015.5"},{"fixed":"2015.5.6"},{"introduced":"2015.8"},{"fixed":"2015.8.1"}]}]

References

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