Approved changes feed: RSS · Atom

cpe:2.3:a:[unknown]:golang:*:*:*:*:*:*:*:*

part: a version: * update: *

Vendor[Unknown] (5b07108a-8f0c-5d28-ab99-c4ff62adb460)
ProductGolang (63f8994d-72b5-5755-a868-7b4875c6e5c0)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2018-16875 vulnerable 2026-06-03 14:38:21.175067 Details available
MEDIUM (5.9)
The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
Published: 2018-12-14T14:00:00.000Z
Updated: 2024-08-05T10:32:54.282Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-16874 vulnerable 2026-06-03 14:38:21.174461 Details available
MEDIUM (6.8)
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path of a malicious Go package which contains curly braces (both '{' and '}' characters). 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). The attacker can cause an arbitrary filesystem write, which can lead to code execution.
Published: 2018-12-14T14:00:00.000Z
Updated: 2024-08-05T10:32:54.222Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-16873 vulnerable 2026-06-03 14:38:21.171590 Details available
HIGH (7.5)
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, they will execute on the system running "go get -u".
Published: 2018-12-14T14:00:00.000Z
Updated: 2024-08-05T10:32:54.055Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.