Количество 29
Количество 29
CVE-2018-16873
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious comma...
CVE-2018-16873
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious comma...
CVE-2018-16873
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious commands
CVE-2018-16873
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is ...
GHSA-q6pp-3q54-qw37
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious comma...
BDU:2020-01887
Уязвимость реализации команды «go get» языка программирования Go, позволяющая нарушителю выполнить произвольный код
openSUSE-SU-2019:0189-1
Security update for docker
openSUSE-SU-2018:4255-1
Security update for go1.10
openSUSE-SU-2018:4181-1
Security update for go1.11
SUSE-SU-2019:0286-1
Security update for docker
SUSE-SU-2019:0048-2
Security update for helm-mirror
SUSE-SU-2019:0048-1
Security update for helm-mirror
openSUSE-SU-2019:1079-1
Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork, runc
openSUSE-SU-2019:0295-1
Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork, runc
openSUSE-SU-2019:0208-1
Security update for runc
openSUSE-SU-2018:4306-1
Security update for containerd, docker and go
SUSE-SU-2019:1264-1
Security update for containerd, docker, docker-runc, go, go1.11, go1.12, golang-github-docker-libnetwork
SUSE-SU-2019:0495-1
Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork, runc
SUSE-SU-2018:4297-1
Security update for containerd, docker and go
openSUSE-SU-2019:1499-1
Security update for containerd, docker, docker-runc, go, go1.11, go1.12, golang-github-docker-libnetwork
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2018-16873 In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious comma... | CVSS3: 8.1 | 61% Средний | около 7 лет назад | |
CVE-2018-16873 In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious comma... | CVSS3: 7.5 | 61% Средний | около 7 лет назад | |
CVE-2018-16873 In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious commands | CVSS3: 8.1 | 61% Средний | около 7 лет назад | |
CVE-2018-16873 In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is ... | CVSS3: 8.1 | 61% Средний | около 7 лет назад | |
GHSA-q6pp-3q54-qw37 In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious comma... | CVSS3: 8.1 | 61% Средний | больше 3 лет назад | |
BDU:2020-01887 Уязвимость реализации команды «go get» языка программирования Go, позволяющая нарушителю выполнить произвольный код | CVSS3: 8.1 | 61% Средний | около 7 лет назад | |
openSUSE-SU-2019:0189-1 Security update for docker | почти 7 лет назад | |||
openSUSE-SU-2018:4255-1 Security update for go1.10 | около 7 лет назад | |||
openSUSE-SU-2018:4181-1 Security update for go1.11 | около 7 лет назад | |||
SUSE-SU-2019:0286-1 Security update for docker | около 7 лет назад | |||
SUSE-SU-2019:0048-2 Security update for helm-mirror | больше 6 лет назад | |||
SUSE-SU-2019:0048-1 Security update for helm-mirror | около 7 лет назад | |||
openSUSE-SU-2019:1079-1 Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork, runc | почти 7 лет назад | |||
openSUSE-SU-2019:0295-1 Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork, runc | почти 7 лет назад | |||
openSUSE-SU-2019:0208-1 Security update for runc | почти 7 лет назад | |||
openSUSE-SU-2018:4306-1 Security update for containerd, docker and go | около 7 лет назад | |||
SUSE-SU-2019:1264-1 Security update for containerd, docker, docker-runc, go, go1.11, go1.12, golang-github-docker-libnetwork | больше 6 лет назад | |||
SUSE-SU-2019:0495-1 Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork, runc | почти 7 лет назад | |||
SUSE-SU-2018:4297-1 Security update for containerd, docker and go | около 7 лет назад | |||
openSUSE-SU-2019:1499-1 Security update for containerd, docker, docker-runc, go, go1.11, go1.12, golang-github-docker-libnetwork | больше 6 лет назад |
Уязвимостей на страницу