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 1546386 - (CVE-2018-7187) CVE-2018-7187 golang: arbitrary command execution via VCS path
CVE-2018-7187 golang: arbitrary command execution via VCS path
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=20180216,repor...
: Security
Depends On: 1565588 1546387 1546388 1566229 1567013 1567014 1611188
Blocks: 1546392
  Show dependency treegraph
 
Reported: 2018-02-16 17:42 EST by Laura Pardo
Modified: 2018-09-27 07:05 EDT (History)
34 users (show)

See Also:
Fixed In Version: golang 1.9.5, golang 1.10.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 Laura Pardo 2018-02-16 17:42:02 EST
A flaw was found in Go Lang. The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only checks for "://" anywhere in the string), which allows remote attackers to execute arbitrary OS commands via a crafted web site.


External References:
https://github.com/golang/go/issues/23867

Upstream Patch:
https://github.com/golang/go/commit/c941e27e70c3e06e1011d2dd71d72a7a06a9bcbc
Comment 1 Laura Pardo 2018-02-16 17:43:26 EST
Created golang tracking bugs for this issue:

Affects: epel-6 [bug 1546387]
Affects: fedora-all [bug 1546388]
Comment 2 Joshua Padman 2018-02-18 19:53:33 EST
golang was included in Red Hat OpenStack 8 & 9 operational tools only as a technical preview for customers, it was provided without support and is not intended to be deployed in production.

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