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.
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
Link | Tags |
---|---|
https://lists.debian.org/debian-lts-announce/2017/12/msg00027.html | third party advisory mailing list |
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.4.1_.282017-11-07.29 | vendor advisory |
https://lists.debian.org/debian-lts-announce/2018/07/msg00041.html | third party advisory mailing list |
https://lists.debian.org/debian-lts-announce/2018/07/msg00005.html | third party advisory mailing list |
https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-November/107333.html | vendor advisory |
http://www.securityfocus.com/bid/102926 | vdb entry third party 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/2020/07/msg00032.html | mailing list |