golang: arbitrary code execution during "go get" or "go get -d"
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 |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Developer Tools | |||
| go-toolset-7-0:1.8-10.el7 | cpe:/a:redhat:devtools:2::el7 | RHSA-2017:3463 | 2017-12-14T00:00:00Z |
| go-toolset-7-golang-0:1.8.5-1.el7 | cpe:/a:redhat:devtools:2::el7 | RHSA-2017:3463 | 2017-12-14T00:00:00Z |
| Red Hat Enterprise Linux 7 | |||
| golang-0:1.9.4-1.el7 | cpe:/o:redhat:enterprise_linux:7 | RHSA-2018:0878 | 2018-04-10T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1148-1 | golang security update |
Debian DLA |
DLA-2591-1 | golang-1.7 security update |
Debian DLA |
DLA-2592-1 | golang-1.8 security update |
EUVD |
EUVD-2017-6516 | Go before 1.8.4 and 1.9.x before 1.9.1 allows "go get" remote command execution. Using custom domains, it is possible to arrange things so that example.com/pkg1 points to a Subversion repository but example.com/pkg1/pkg2 points to a Git repository. If the Subversion repository includes a Git checkout in its pkg2 directory and some other work is done to ensure the proper ordering of operations, "go get" can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository's Git checkout has malicious commands in .git/hooks/, they will execute on the system running "go get." |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 8.9% (8.944% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.