← Back
CVE-2016-3068
Vulnerability in mercurial (CVE-2016-3068)
Summary
vulnerability in mercurial (CVE-2016-3068). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.7.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2016-3068** has been found in mercurial.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade mercurial to **3.7.3** or later.
If unsure, ask your IT team or search "mercurial CVE-2016-3068" on the vendor's site.
CVE-2016-3068 (mercurial) —
Patched: `3.7.3` — 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** (unclassified) exists in mercurial.
📍 Affected scope
mercurial — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.7.3**.
🛡️ 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 3.7.3ステージング環境で 3.7.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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":"3.7.3"}]}]
References
- advisory http://www.debian.org/security/2016/dsa-3542
- advisory http://rhn.redhat.com/errata/RHSA-2016-0706.html
- advisory https://security.gentoo.org/glsa/201612-19
- advisory https://github.com/advisories/GHSA-j7c2-rqm3-c97m
- web http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00018.html
- web http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00017.html
- web http://lists.fedoraproject.org/pipermail/package-announce/2016-April/181505.html
- web https://selenic.com/repo/hg-stable/rev/34d43cb85de8
- web https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.7.3_.282016-3-29.29
- web http://lists.fedoraproject.org/pipermail/package-announce/2016-April/181542.html
- web http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00016.html
- web http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00043.html
- web http://www.oracle.com/technetwork/topics/security/linuxbulletinapr2016-2952096.html
- web http://www.oracle.com/technetwork/topics/security/bulletinapr2016-2952098.html
- web http://www.securityfocus.com/bid/85733