"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 in to the repository in Mercurial 4.4 and earlier. Typical use
of Mercurial prevents construction of such repositories, but they can be
created programmatically."
https://www.mercurial-scm.org/pipermail/mercurial/2017-August/050522.html
CVE-2017-1000115:
Mercurial's symlink auditing was incomplete prior to 4.3, and could be abused
to write to files outside the repository.
CVE-2017-1000116:
Mercurial was not sanitizing hostnames passed to ssh, allowing shell injection
attacks by specifying a hostname starting with -oProxyCommand.
SECURITY: "hg serve --stdio could be tricked into granting authorized
users access to the Python debugger"
"dispatch: protect against malicious 'hg serve --stdio' invocations
(sec) Some shared-ssh installations assume that 'hg serve --stdio' is
a safe command to run for minimally trusted users. Unfortunately, the
messy implementation of argument parsing here meant that trying to
access a repo named '--debugger' would give the user a pdb prompt,
thereby sidestepping any hoped-for sandboxing. Serving repositories
over HTTP(S) is unaffected.
We're not currently hardening any subcommands other than 'serve'. If
your service exposes other commands to users with arbitrary repository
names, it is imperative that you defend against repository names of
'--debugger' and anything starting with '--config'.
The read-only mode of hg-ssh stopped working because it provided its
hook configuration to "hg serve --stdio" via --config parameter. This
is banned for security reasons now. This patch switches it to directly
call ui.setconfig(). If your custom hosting infrastructure relies on
passing --config to "hg serve --stdio", you'll need to find a
different way to get that configuration into Mercurial, either by
using ui.setconfig() as hg-ssh does in this patch, or by placing an
hgrc file someplace where Mercurial will read it. mitrandir@fb.com
provided some extra fixes for the dispatch code and for hg-ssh in
places that I overlooked."
* Make graphical tooling for mercurial a subpackage (like the git port).
* Bump all RUN/LIB dependants of mercurial to reflect new pkgpath.
* Make 'hg view' work without custom paths in hgrc.
* Substitute some shebangs in the example mercurial scripts.
OK ajacoutot@
