CVE-2017-17458: Mercurial vulnerable to arbitrary code injection

CVE-2017-17458 · Severity: low · CVSS 3 · Published 2017-12-07

In Mercurial before 4.4.1, it is possible that a specially malformed repository can cause Git subrepositories to run arbitrary code in the form of a .git/hooks/post-update script checked into the repository. Typical use of Mercurial prevents construction of such repositories, but they can be created programmatically.

Technologies: mercurial (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2017-17458 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-17458 being exploited in the wild.
How severe is CVE-2017-17458?
Low severity, with a CVSS score of 3, published 7 December 2017.
Which products and versions are affected?
mercurial (PyPI) ECOSYSTEM:introduced=0,fixed=4.4.1.
Is there a fix for CVE-2017-17458?
Yes. mercurial (PyPI): upgrade to 4.4.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-17458?
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.4.1 or later
    pip install "mercurial>=4.4.1"

Affected products

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

Identifiers

  • CVE-2017-17458
  • GHSA-6v56-cpg6-3rpx
  • PYSEC-2017-90

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