Vulnerabilities · 2017 · Mercurial
CVE-2017-17458
Mercurial vulnerability
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Mercurial, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Mercurial runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.mercurial-scm.org/pipermail/mercurial-devel/2017-November/107333.html · Vendor Advisory
- www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.4.1_.282017-11-07.29 · Vendor Advisory
- www.securityfocus.com/bid/102926 · Third Party Advisory
- bz.mercurial-scm.org/show_bug.cgi?id=5730 · Third Party Advisory
- confluence.atlassian.com/sourcetreekb/sourcetree-security-advisory-2018-01-24-942834324.ht · Third Party Advisory
- lists.debian.org/debian-lts-announce/2017/12/msg00027.html · Third Party Advisory
- lists.debian.org/debian-lts-announce/2018/07/msg00005.html · Third Party Advisory
- lists.debian.org/debian-lts-announce/2018/07/msg00041.html · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2017-17458
- cve.org/CVERecord?id=CVE-2017-17458
More vulnerabilities in Mercurial products
CVE-2019-3902CVE-2018-1000132CVE-2018-17983CVE-2018-13348CVE-2018-13347CVE-2018-13346CVE-2017-1000116CVE-2017-1000115All 19
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.