First published: Thu Aug 10 2017(Updated: )
Mercurial prior to version 4.3 is vulnerable to a missing symlink check that can malicious repositories to modify files outside the repository
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/mercurial | <4.3 | 4.3 |
redhat/mercurial | <4.2.3 | 4.2.3 |
pip/mercurial | <4.3.1 | 4.3.1 |
Mercurial | <4.3 | |
Debian Linux | =8.0 | |
Debian Linux | =9.0 | |
Red Hat Enterprise Linux Desktop | =7.0 | |
Red Hat Enterprise Linux Server | =7.0 | |
Red Hat Enterprise Linux Server | =7.4 | |
Red Hat Enterprise Linux Server | =7.6 | |
Red Hat Enterprise Linux Server | =7.4 | |
Red Hat Enterprise Linux Server | =7.5 | |
Red Hat Enterprise Linux Server | =7.6 | |
Red Hat Enterprise Linux Server | =7.4 | |
Red Hat Enterprise Linux Server | =7.6 | |
Red Hat Enterprise Linux Workstation | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000115 is classified as a moderate severity vulnerability due to the potential for unintended file modifications in malicious repositories.
To fix CVE-2017-1000115, update Mercurial to version 4.3 or later, or to version 4.2.3 if using an older release.
CVE-2017-1000115 affects Mercurial versions prior to 4.3 on various Linux distributions including Red Hat and Debian.
CVE-2017-1000115 can allow a malicious repository to modify files outside of the intended directory by exploiting the missing symlink check.
CVE-2017-1000115 can be exploited remotely as it involves malicious repositories that can affect local file systems.