cmd-go on Go The code injection

Summaryinfo

A vulnerability marked as critical has been reported in cmd-go on Go. Impacted is an unknown function. The manipulation of the argument The leads to code injection. This vulnerability is uniquely identified as CVE-2023-29404. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in cmd-go on Go (the affected version is unknown). It has been rated as critical. This issue affects an unknown code. The manipulation of the argument The with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The go command may execute arbitrary code at build time when using cgo. This may occur when running "go get" on a malicious module, or when running any other command which builds untrusted code. This is can by triggered by linker flags, specified via a "#cgo LDFLAGS" directive. The arguments for a number of flags which are non-optional are incorrectly considered optional, allowing disallowed flags to be smuggled through the LDFLAGS sanitization. This affects usage of both the gc and gccgo compilers.

The weakness was disclosed 06/09/2023. The advisory is shared at go.dev. The identification of this vulnerability is CVE-2023-29404 since 04/05/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 276422 (TencentOS Server 3: go-toolset:rhel8 (TSSA-2023:0177)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (276422). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• cmd-go

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion