Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1594090 - (CVE-2018-13346) CVE-2018-13346 mercurial: Missing check for fragment start position in mpatch.c:mpatch_apply()
CVE-2018-13346 mercurial: Missing check for fragment start position in mpatch...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180606,reported=2...
: Security
Depends On: 1594088 1594089 1613129
Blocks: 1594086
  Show dependency treegraph
 
Reported: 2018-06-22 00:49 EDT by Sam Fowler
Modified: 2018-09-30 18:13 EDT (History)
6 users (show)

See Also:
Fixed In Version: mercurial 4.6.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-06-22 00:49:21 EDT
Mercurial before version 4.6.1 has a missing check for fragment start position in mpatch.c:mpatch_apply()

Upstream Changelog:

https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.6.1_.282018-06-06.29


Upstream Patch:

https://www.mercurial-scm.org/repo/hg/rev/faa924469635
Comment 1 Doran Moppert 2018-07-27 00:52:14 EDT
This is related to CVE-2018-13347: this issue is reading past the end of input where the other writes before the output buffer.  In mercurial 2.6.2, it is present in the apply() function.
Comment 2 Doran Moppert 2018-08-07 01:08:19 EDT
Created mercurial tracking bugs for this issue:

Affects: fedora-all [bug 1594088]

Note You need to log in before you can comment on or make changes to this bug.