CVE-2023-29404: Improper handling of non-optional LDFLAGS in go command with cgo in cmd/go
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Go toolchain cmd/go 1.19.10, 1.20.5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to Go toolchain cmd/go 1.19.10, 1.20.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 8, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-94
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| golang | go | cpe:2.3:a:golang:go |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora38
- golang gobefore 1.19.10
- golang go1.20.0 and later · before 1.20.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.
Go toolchain cmd/go
- before 1.19.10affected · semver
- 1.20.0-0 and later · before 1.20.5affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | delve | before 1.9.1-1.module_el8.8.0+3471+a62632a0 | 1.9.1-1.module_el8.8.0+3471+a62632a0 |
| AlmaLinux:8 | go-toolset | before 1.19.10-1.module_el8.8.0+3571+89db2ae0 | 1.19.10-1.module_el8.8.0+3571+89db2ae0 |
| AlmaLinux:8 | golang | before 1.19.10-1.module_el8.8.0+3571+89db2ae0 | 1.19.10-1.module_el8.8.0+3571+89db2ae0 |
| AlmaLinux:8 | golang-bin | before 1.19.10-1.module_el8.8.0+3571+89db2ae0 | 1.19.10-1.module_el8.8.0+3571+89db2ae0 |
| AlmaLinux:8 | golang-docs | before 1.19.10-1.module_el8.8.0+3571+89db2ae0 | 1.19.10-1.module_el8.8.0+3571+89db2ae0 |
| AlmaLinux:8 | golang-misc | before 1.19.10-1.module_el8.8.0+3571+89db2ae0 | 1.19.10-1.module_el8.8.0+3571+89db2ae0 |
| AlmaLinux:8 | golang-race | before 1.19.10-1.module_el8.8.0+3571+89db2ae0 | 1.19.10-1.module_el8.8.0+3571+89db2ae0 |
| AlmaLinux:8 | golang-src | before 1.19.10-1.module_el8.8.0+3571+89db2ae0 | 1.19.10-1.module_el8.8.0+3571+89db2ae0 |
| AlmaLinux:8 | golang-tests | before 1.19.10-1.module_el8.8.0+3571+89db2ae0 | 1.19.10-1.module_el8.8.0+3571+89db2ae0 |
| AlmaLinux:9 | go-toolset | before 1.19.10-1.el9_2 | 1.19.10-1.el9_2 |
| AlmaLinux:9 | golang | before 1.19.10-1.el9_2 | 1.19.10-1.el9_2 |
| AlmaLinux:9 | golang-bin | before 1.19.10-1.el9_2 | 1.19.10-1.el9_2 |
| AlmaLinux:9 | golang-docs | before 1.19.10-1.el9_2 | 1.19.10-1.el9_2 |
| AlmaLinux:9 | golang-misc | before 1.19.10-1.el9_2 | 1.19.10-1.el9_2 |
| AlmaLinux:9 | golang-race | before 1.19.10-1.el9_2 | 1.19.10-1.el9_2 |
| AlmaLinux:9 | golang-src | before 1.19.10-1.el9_2 | 1.19.10-1.el9_2 |
| AlmaLinux:9 | golang-tests | before 1.19.10-1.el9_2 | 1.19.10-1.el9_2 |
| Debian:12 | golang-1.19 | from 0 | — |
| Go | toolchain | from 1.20.0-0 · before 1.20.5 | 1.20.5 |
| Go | toolchain | before 1.19.10 | 1.19.10 |
| openSUSE:Leap 15.4 | go1.19 | before 1.19.10-150000.1.34.1 | 1.19.10-150000.1.34.1 |
| openSUSE:Leap 15.4 | go1.20 | before 1.20.5-150000.1.14.1 | 1.20.5-150000.1.14.1 |
| openSUSE:Tumbleweed | go1.19 | before 1.19.10-1.1 | 1.19.10-1.1 |
| openSUSE:Tumbleweed | go1.20 | before 1.20.5-1.1 | 1.20.5-1.1 |
+34
Same product
golang: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only 54Plan
- CVE-2018-16873In 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 and52Plan
- CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH42Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-29402Jun 8, 2023 · Code injection via go command with cgo in cmd/go40Plan
- ← EarlierCVE-2023-29403Jun 8, 2023 · Unsafe behavior in setuid/setgid binaries in runtime31Monitor
- Later →CVE-2023-29405Jun 8, 2023 · Improper sanitization of LDFLAGS with embedded spaces in go command with cgo in cmd/go40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go toolchain cmd/go | 1.19.10 | Vendor (CNA) |
| Go toolchain cmd/go | 1.20.5 | Vendor (CNA) |
| almalinux:delve | 1.9.1-1.module_el8.8.0+3471+a62632a0 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:go-toolset | 1.19.10-1.module_el8.8.0+3571+89db2ae0 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:golang | 1.19.10-1.module_el8.8.0+3571+89db2ae0 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:golang-bin | 1.19.10-1.module_el8.8.0+3571+89db2ae0 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:golang-docs | 1.19.10-1.module_el8.8.0+3571+89db2ae0 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:golang-misc | 1.19.10-1.module_el8.8.0+3571+89db2ae0 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:golang-race | 1.19.10-1.module_el8.8.0+3571+89db2ae0 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:golang-src | 1.19.10-1.module_el8.8.0+3571+89db2ae0 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:golang-tests | 1.19.10-1.module_el8.8.0+3571+89db2ae0 · AlmaLinux:8 | Package registry (OSV) |
| Go:toolchain | 1.19.10 | Package registry (OSV) |
| Go:toolchain | 1.20.5 | Package registry (OSV) |
| opensuse:go1.19 | 1.19.10-150000.1.34.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:go1.20 | 1.20.5-150000.1.14.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:delve | 0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:go-toolset-1.19 | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-build | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-golang | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-golang-bin | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-golang-docs | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-golang-misc | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-golang-race | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-golang-src | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-golang-tests | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-runtime | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| red hat:go-toolset-1.19-scldevel | 0:1.19.10-1.el7_9 · Red Hat:devtools:2023::el7 | Package registry (OSV) |
| rocky linux:go-toolset | 0:1.19.10-1.el9_2 · Rocky Linux:9 | Package registry (OSV) |
| rocky linux:golang | 0:1.19.10-1.el9_2 · Rocky Linux:9 | Package registry (OSV) |
| suse:go1.19 | 1.19.10-150000.1.34.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
+1
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Juho NurminenMattermost
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0714 · Dec 19, 2023(IBM Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- go.dev/issue/60305
- groups.google.com/g/golang-announce/c/q5135a9d924/m/j0ZoAJOHAwAJ
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NZ2O6YCO2IZMZJELQGZYR2WAUNEDLYV6/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XBS3IIK6ADV24C5ULQU55QLT2UE762ZX/
- pkg.go.dev/vuln/GO-2023-1841
- security.gentoo.org/glsa/202311-09
- security.netapp.com/advisory/ntap-20241115-0009/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.