# CVE-2023-29404: Improper handling of non-optional LDFLAGS in go command with cgo in cmd/go

> Attackers can execute arbitrary code during build time by exploiting improper LDFLAGS sanitization in the Go command when using cgo.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jun 2023
- **Updated:** 6 Jan 2025
- **Also known as:** AZL-27140, AZL-27150, AZL-37337, AZL-37510, AZL-47146, BIT-golang-2023-29404, DEBIAN-CVE-2023-29404, GHSA-888h-rm2r-vrc7, GO-2023-1841, MINI-ggfp-xjv3-54hc, UBUNTU-CVE-2023-29404

## What is CVE-2023-29404?

CVE-2023-29404 is a critical code injection vulnerability in Fedoraproject Fedora, published on 8 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-29404?

2 open source packages ship an affected version, including golang and toolchain. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.19.10, 1.20.5 |
| `toolchain` | Go | All versions | 1.19.10, 1.20.5 |

Products: Fedoraproject Fedora, Golang Go.

## How do I fix CVE-2023-29404?

Upgrade golang to a fixed version for your release line: 1.19.10 or 1.20.5.

## Is CVE-2023-29404 being exploited?

There is no known exploitation of CVE-2023-29404 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29404 and fix it if it is affected.

What it is: CVE-2023-29404 is a critical code injection vulnerability in Fedoraproject Fedora, published on 8 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-29404 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.19.10, 1.20.5
- toolchain (Go): affected all versions; fixed in 1.19.10, 1.20.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-29404/ (Markdown: https://insights.sbomify.com/CVE-2023-29404/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-29404
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-29404
- OSV: https://osv.dev/vulnerability/CVE-2023-29404

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-29404/
Summaries are generated and may contain mistakes; the official description above is the record.