CVE-2017-15041: Critical severity Golang Go vulnerability

Published Oct 5, 2017
·
Updated

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."

Other sources

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 a malicious code in .git/hooks/, it will execute on the system running “go get.”

Upstream bug:

https://github.com/golang/go/issues/22125

Upstream patches:

Go 1.8: https://go-review.googlesource.com/c/go/+/68190 Go 1.9: https://go-review.googlesource.com/c/go/+/68022

Red Hat

Affected Software

13 affected componentsFixes available
redhat/golang<1.8.4
1.8.4
redhat/golang<1.9.1
1.9.1
Golang Go<=1.8.3
Golang Go=1.9
Debian Debian Linux=9.0
redhat Developer Tools=1.0
redhat Enterprise Linux Eus=7.6
redhat Enterprise Linux Eus=7.7
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Tus=7.6
redhat Enterprise Linux Tus=7.7

Event History

Oct 5, 2017
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-15041?

CVE-2017-15041 has a high severity due to the potential for remote command execution.

2

How do I fix CVE-2017-15041?

To fix CVE-2017-15041, upgrade Golang to version 1.8.4 or above for 1.8.x, or to version 1.9.1 or above for 1.9.x.

3

What versions of Golang are affected by CVE-2017-15041?

CVE-2017-15041 affects Golang versions prior to 1.8.4 and 1.9.x prior to 1.9.1.

4

Which operating systems are impacted by CVE-2017-15041?

CVE-2017-15041 impacts various distributions of Linux that utilize the affected versions of Golang.

5

Is CVE-2017-15041 a known vulnerability?

Yes, CVE-2017-15041 is a publicly known vulnerability affecting specific versions of Golang.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203