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 1332945 - (CVE-2016-3105) CVE-2016-3105 mercurial: arbitrary code execution when converting git repos
CVE-2016-3105 mercurial: arbitrary code execution when converting git repos
Status: NEW
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=20160406,repor...
: Security
Depends On: 1332946
Blocks: 1332947
  Show dependency treegraph
 
Reported: 2016-05-04 08:08 EDT by Andrej Nemec
Modified: 2016-11-08 11:08 EST (History)
3 users (show)

See Also:
Fixed In Version: mercurial 3.8
Doc Type: Bug Fix
Doc Text:
It was discovered that the Mercurial convert extension invoked Git in a way that could cause Git to interpret local repository name as remote repository URL. A Git repository with a specially crafted name could cause Mercurial to execute arbitrary code when the Git repository was converted to a Mercurial repository.
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 Andrej Nemec 2016-05-04 08:08:37 EDT
A possible arbitrary code execution when converting Git repos was found in Mercirual.  Mercurial prior to 3.8 allowed arbitrary code execution when using the convert extension on Git repos with hostile names. This could affect automated code conversion services that allow arbitrary repository names. This is a further side-effect of Git CVE-2015-7545.

External Reference:

https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.8_.2F_3.8.1_.282016-5-1.29

Upstream fix:

https://selenic.com/hg/rev/a56296f55a5e
Comment 1 Andrej Nemec 2016-05-04 08:09:01 EDT
Created mercurial tracking bugs for this issue:

Affects: fedora-all [bug 1332946]

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