Arbitrary code execution via smuggled linker flags
Published Jun 8, 2023 · Updated Jan 6, 2025
Linker-flag injection in Go cmd/go and cmd/cgo before 1.19.10 and 1.20.0 through 1.20.4 allows attackers to execute code during builds. With gccgo, embedded spaces in a #cgo LDFLAGS argument let a disallowed linker option pass sanitization as part of another option's argument. Execution requires building attacker-controlled code with cgo and gccgo, including fetching a malicious module, and runs with the builder's privileges.
Summary
What happened
Linker-flag injection in Go cmd/go and cmd/cgo before 1.19.10 and 1.20.0 through 1.20.4 allows attackers to execute code during builds. With gccgo, embedded spaces in a #cgo LDFLAGS argument let a disallowed linker option pass sanitization as part of another option's argument. Execution requires building attacker-controlled code with cgo and gccgo, including fetching a malicious module, and runs with the builder's privileges.
The record
- CVE
- CVE-2023-29405
- Published
- Jun 8, 2023
- Updated
- Jan 6, 2025
- Vendor
- Go
- Product
- Go command
- Classifications
- CWE-74, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 8, 2023CVE publishedPublication date reported by the CVE source.
- Jan 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.19.10
- Affected versionversion=1.20.0-0 <1.20.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo