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 1594083 - (CVE-2018-13348) CVE-2018-13348 mercurial: Improper length check in mpatch.c
CVE-2018-13348 mercurial: Improper length check in mpatch.c
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180606,repor...
: Security
Depends On: 1594084 1594085
Blocks: 1594086
  Show dependency treegraph
 
Reported: 2018-06-22 00:35 EDT by Sam Fowler
Modified: 2018-07-27 00:51 EDT (History)
7 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: 2018-07-27 00:51:52 EDT
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:35:41 EDT
Mercurial before version 4.6.1 does not properly check the length of binary patch data.


Upstream Changelog:

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


Upstream Patches:

https://www.mercurial-scm.org/repo/hg/rev/90a274965de7
Comment 1 Sam Fowler 2018-06-22 00:36:08 EDT
Created mercurial tracking bugs for this issue:

Affects: fedora-all [bug 1594084]
Comment 3 Doran Moppert 2018-07-27 00:47:36 EDT
In earlier versions of mercurial (inc 2.6.2), the pointer was maintained at the end of the region that would be read, so overflow was not possible.

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