https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 12:16:34 +0000 https://cve.radiocsirt.org/vuln/cnvd-2017-30861 cnvd-2017-30861 https://cve.radiocsirt.org/vuln/cnvd-2017-30861 https://cve.radiocsirt.org/vuln/euvd-2026-78399 EUVD-2026-78399 https://cve.radiocsirt.org/vuln/euvd-2026-78399 https://cve.radiocsirt.org/vuln/fkie_cve-2017-15041 <p>Go before 1.8.4 and 1.9.x before 1.9.1 allows &#34;go get&#34; 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, &#34;go get&#34; can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository&#39;s Git checkout has malicious commands in .git/hooks/, they will execute on the system running &#34;go get.&#34;</p> <p>Go before 1.8.4 and 1.9.x before 1.9.1 allows &#34;go get&#34; 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, &#34;go get&#34; can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository&#39;s Git checkout has malicious commands in .git/hooks/, they will execute on the system running &#34;go get.&#34;</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-15041 https://cve.radiocsirt.org/vuln/ghsa-2w49-qg9p-7jxx <p>Go before 1.8.4 and 1.9.x before 1.9.1 allows &#34;go get&#34; 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, &#34;go get&#34; can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository&#39;s Git checkout has malicious commands in .git/hooks/, they will execute on the system running &#34;go get.&#34;</p> <p>Go before 1.8.4 and 1.9.x before 1.9.1 allows &#34;go get&#34; 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, &#34;go get&#34; can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository&#39;s Git checkout has malicious commands in .git/hooks/, they will execute on the system running &#34;go get.&#34;</p> https://cve.radiocsirt.org/vuln/ghsa-2w49-qg9p-7jxx https://cve.radiocsirt.org/vuln/gsd-2017-15041 gsd-2017-15041 https://cve.radiocsirt.org/vuln/gsd-2017-15041 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10802-1 <p>go-1.17-1.1 on GA media</p> <p>go-1.17-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10802-1 https://cve.radiocsirt.org/vuln/rhsa-2017:3463 <p>golang: arbitrary code execution during &#34;go get&#34; or &#34;go get -d&#34; golang: smtp.PlainAuth susceptible to man-in-the-middle password harvesting</p> <p>golang: arbitrary code execution during &#34;go get&#34; or &#34;go get -d&#34; golang: smtp.PlainAuth susceptible to man-in-the-middle password harvesting</p> https://cve.radiocsirt.org/vuln/rhsa-2017:3463 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-15041 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: golang-1.6, Ubuntu:18.04:LTS: golang-1.8</p> <p>Go before 1.8.4 and 1.9.x before 1.9.1 allows &#34;go get&#34; 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, &#34;go get&#34; can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository&#39;s Git checkout has malicious commands in .git/hooks/, they will execute on the system running &#34;go get.&#34;</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: golang-1.6, Ubuntu:18.04:LTS: golang-1.8</p> <p>Go before 1.8.4 and 1.9.x before 1.9.1 allows &#34;go get&#34; 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, &#34;go get&#34; can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository&#39;s Git checkout has malicious commands in .git/hooks/, they will execute on the system running &#34;go get.&#34;</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-15041