CVE-2017-1000115: Mercurial missing symlink check

CVE-2017-1000115 · Severity: low · CVSS 3 · Published 2017-10-05

Mercurial prior to version 4.3 is vulnerable to a missing symlink check that can malicious repositories to modify files outside the repository

Technologies: mercurial (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2017-1000115 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-1000115 being exploited in the wild.
How severe is CVE-2017-1000115?
Low severity, with a CVSS score of 3, published 5 October 2017.
Which products and versions are affected?
mercurial (PyPI) ECOSYSTEM:introduced=0,fixed=4.3, ECOSYSTEM:introduced=0,fixed=4.3.1.
Is there a fix for CVE-2017-1000115?
Yes. mercurial (PyPI): upgrade to 4.3, 4.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-1000115?
Check whether you run mercurial (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • mercurial (PyPI): upgrade to 4.3, 4.3.1 or later
    pip install "mercurial>=4.3.1"

Affected products

  • mercurial (PyPI) ECOSYSTEM:introduced=0,fixed=4.3, ECOSYSTEM:introduced=0,fixed=4.3.1

Identifiers

  • CVE-2017-1000115
  • GHSA-hvr9-wr9p-grgr
  • PYSEC-2017-88

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.