First published: Fri Jun 22 2018(Updated: )
Mercurial before version 4.6.1 has a missing check for fragment start position in mpatch.c:mpatch_apply() Upstream Changelog: <a href="https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.6.1_.282018-06-06.29">https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.6.1_.282018-06-06.29</a> Upstream Patch: <a href="https://www.mercurial-scm.org/repo/hg/rev/faa924469635">https://www.mercurial-scm.org/repo/hg/rev/faa924469635</a>
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Mercurial Mercurial | <4.6.1 | |
redhat/mercurial | <4.6.1 | 4.6.1 |
pip/mercurial | <4.6.1 | 4.6.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-13346 is a vulnerability in Mercurial before 4.6.1 that allows the mpatch_apply function in mpatch.c to incorrectly proceed in cases where the fragment start is past the end of the original data.
The severity of CVE-2018-13346 is high, with a CVSS score of 7.5.
Versions of Mercurial before 4.6.1 are affected by CVE-2018-13346.
To fix CVE-2018-13346, update Mercurial to version 4.6.1 or later.
More information about CVE-2018-13346 can be found at the following references: [Link 1](https://access.redhat.com/errata/RHSA-2019:2276), [Link 2](https://lists.debian.org/debian-lts-announce/2020/07/msg00032.html), [Link 3](https://www.mercurial-scm.org/repo/hg/rev/faa924469635).