← Back
CVE-2017-17458
critical
CVSS 9.8
OS Command Injection in mercurial (CVE-2017-17458)
Summary
OS command injection in mercurial (CVE-2017-17458). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `4.4.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2017-17458** has been found in mercurial.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade mercurial to **4.4.1** or later.
If unsure, ask your IT team or search "mercurial CVE-2017-17458" on the vendor's site.
CVE-2017-17458 (mercurial) — CWE-78 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `4.4.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
**OS command injection** (CWE-78) exists in mercurial.
📍 Affected scope
mercurial — .
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **4.4.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 'mercurial' .` 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 'mercurial' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mercurial` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mercurial to 4.4.1ステージング環境で 4.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
mercurial
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.1"}]}]
References
- advisory https://confluence.atlassian.com/sourcetreekb/sourcetree-security-advisory-2018-01-24-942834324.html
- advisory https://github.com/advisories/GHSA-6v56-cpg6-3rpx
- web http://www.securityfocus.com/bid/102926
- web https://bz.mercurial-scm.org/show_bug.cgi?id=5730
- web https://lists.debian.org/debian-lts-announce/2017/12/msg00027.html
- web https://lists.debian.org/debian-lts-announce/2018/07/msg00005.html
- web https://lists.debian.org/debian-lts-announce/2018/07/msg00041.html
- web https://lists.debian.org/debian-lts-announce/2020/07/msg00032.html
- web https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-November/107333.html
- web https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.4.1_.282017-11-07.29