pysec-2018-88
Vulnerability from pysec
Published
2018-07-06 00:29
Modified
2021-08-27 03:22
Details
The mpatch_apply function in mpatch.c in Mercurial before 4.6.1 incorrectly proceeds in cases where the fragment start is past the end of the original data, aka OVE-20180430-0004.
Impacted products
Name | purl |
---|---|
mercurial | pkg:pypi/mercurial |
Aliases
{ affected: [ { package: { ecosystem: "PyPI", name: "mercurial", purl: "pkg:pypi/mercurial", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "4.6.1", }, ], type: "ECOSYSTEM", }, ], versions: [ "0.8.1", "0.9", "0.9.1", "0.9.2", "0.9.3", "0.9.4", "0.9.5", "1.0", "1.0.1", "1.0.2", "1.1", "1.1.1", "1.1.2", "1.2", "1.2.1", "1.3", "1.3.1", "1.4", "1.4.1", "1.4.2", "1.4.3", "1.5", "1.5.1", "1.5.2", "1.5.3", "1.5.4", "1.6", "1.6.1", "1.6.2", "1.6.3", "1.6.4", "1.7", "1.7.1", "1.7.2", "1.7.3", "1.7.5", "1.8", "1.8.1", "1.8.2", "1.8.3", "1.8.4", "1.9", "1.9.1", "1.9.2", "1.9.3", "2.0", "2.0.1", "2.0.2", "2.1", "2.1.1", "2.1.2", "2.2", "2.2.2", "2.3", "2.4.1", "2.5", "2.5.1", "2.5.2", "2.6", "2.6.1", "2.6.2", "2.6.3", "2.7.0", "2.7.1", "2.7.2", "2.8", "2.8.1", "2.8.2", "2.9", "2.9.1", "3.0", "3.0.1", "3.1", "3.1.1", "3.1.2", "3.2", "3.2.1", "3.2.2", "3.2.3", "3.2.4", "3.3", "3.3-rc", "3.3.1", "3.3.2", "3.3.3", "3.4", "3.4-rc", "3.4.1", "3.4.2", "3.5", "3.5-rc", "3.5.1", "3.5.2", "3.6", "3.6-rc", "3.6.1", "3.6.2", "3.6.3", "3.7", "3.7-rc", "3.7.1", "3.7.2", "3.7.3", "3.8", "3.8-rc", "3.8.1", "3.8.2", "3.8.3", "3.8.4", "3.9", "3.9-rc", "3.9.1", "3.9.2", "4.0", "4.0-rc", "4.0.1", "4.0.2", "4.1", "4.1-rc", "4.1.1", "4.1.2", "4.1.3", "4.2", "4.2-rc", "4.2.1", "4.2.2", "4.2.3", "4.3", "4.3-rc", "4.3.1", "4.3.2", "4.3.3", "4.3rc0", "4.4", "4.4-rc", "4.4.1", "4.4.2", "4.4rc0", "4.5", "4.5-rc", "4.5.1", "4.5.2", "4.5.3", "4.5rc0", "4.6", "4.6rc0", "4.6rc1", ], }, ], aliases: [ "CVE-2018-13346", ], details: "The mpatch_apply function in mpatch.c in Mercurial before 4.6.1 incorrectly proceeds in cases where the fragment start is past the end of the original data, aka OVE-20180430-0004.", id: "PYSEC-2018-88", modified: "2021-08-27T03:22:07.239369Z", published: "2018-07-06T00:29:00Z", references: [ { type: "WEB", url: "https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.6.1_.282018-06-06.29", }, { type: "WEB", url: "https://www.mercurial-scm.org/repo/hg/rev/faa924469635", }, { type: "ADVISORY", url: "https://access.redhat.com/errata/RHSA-2019:2276", }, { type: "WEB", url: "https://lists.debian.org/debian-lts-announce/2020/07/msg00032.html", }, ], }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.