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.
References
Link | Resource |
---|---|
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.4.1_.282017-11-07.29 | Vendor Advisory |
https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-November/107333.html | Vendor Advisory |
https://bz.mercurial-scm.org/show_bug.cgi?id=5730 | Issue Tracking Third Party Advisory |
https://confluence.atlassian.com/sourcetreekb/sourcetree-security-advisory-2018-01-24-942834324.html | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2017/12/msg00027.html | Mailing List Third Party Advisory |
http://www.securityfocus.com/bid/102926 | Third Party Advisory VDB Entry |
https://lists.debian.org/debian-lts-announce/2018/07/msg00005.html | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2018/07/msg00041.html | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2020/07/msg00032.html |
Information
Published : 2017-12-07 10:29
Updated : 2020-07-31 06:15
NVD link : CVE-2017-17458
Mitre link : CVE-2017-17458
JSON object : View
CWE
CWE-78
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Products Affected
debian
- debian_linux
mercurial
- mercurial