mercurial: Missing check for fragment start position in mpatch.c:mpatch_apply()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | |||
| mercurial-0:2.6.2-10.el7 | cpe:/o:redhat:enterprise_linux:7 | RHSA-2019:2276 | 2019-08-06T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2293-1 | mercurial security update |
EUVD |
EUVD-2018-0095 | 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. |
Github GHSA |
GHSA-9xv4-r2hf-26gh | Mercurial Improper Input Validation vulnerability |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 2.4% (2.365% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.