CVE-2017-15041

Description

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

9.8

CVSS

Severity: Critical

CVSS 3.1 •

CVSS 2.0 •

EPSS 6.02% Top 10%

Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory gentoo.org Vendor Advisory golang.org Vendor Advisory golang.org Vendor Advisory google.com

Affected: n/a n/a

References

Link	Tags
https://access.redhat.com/errata/RHSA-2017:3463	third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2018:0878	third party advisory vendor advisory
https://golang.org/cl/68190	patch vendor advisory issue tracking
http://www.securityfocus.com/bid/101196	third party advisory vdb entry
https://golang.org/cl/68022	patch vendor advisory issue tracking
https://security.gentoo.org/glsa/201710-23	third party advisory vendor advisory
https://groups.google.com/d/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJ	vendor advisory mailing list
https://github.com/golang/go/issues/22125	patch third party advisory issue tracking
https://lists.debian.org/debian-lts-announce/2021/03/msg00014.html	third party advisory mailing list
https://lists.debian.org/debian-lts-announce/2021/03/msg00015.html	third party advisory mailing list

Frequently Asked Questions

What is the severity of CVE-2017-15041?: CVE-2017-15041 has been scored as a critical severity vulnerability.
How to fix CVE-2017-15041?: To fix CVE-2017-15041, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-15041 being actively exploited in the wild?: It is possible that CVE-2017-15041 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~6% probability that this vulnerability will be exploited by malicious actors in the next 30 days.