Mercurial vulnerable to arbitrary code injection
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-17458US | critical9.8 | — | ||
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 c… | ||||
02
references
External citations — patches, advisories, analysis.
- https://bz.mercurial-scm.org/show_bug.cgi?id=5730WEB
- https://confluence.atlassian.com/sourcetreekb/sourcetree-security-advisory-2018-01-24-942834324.htmlWEB
- https://github.com/dscho/hgPACKAGE
- https://github.com/pypa/advisory-database/tree/main/vulns/mercurial/PYSEC-2017-90.yamlWEB
- https://lists.debian.org/debian-lts-announce/2017/12/msg00027.htmlWEB
- https://lists.debian.org/debian-lts-announce/2018/07/msg00005.htmlWEB
- https://lists.debian.org/debian-lts-announce/2018/07/msg00041.htmlWEB
- https://lists.debian.org/debian-lts-announce/2020/07/msg00032.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan