Arbitrary command execution via GCC spec files in cgo linker search directories in cmd/go
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.26.11, 1.27.4 and toolchain 1.27.4.
When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files ("specs" or "*.spec"). When linking with "-fopenmp", "-fopenacc", or "-fsanitize=" in "#cgo LDFLAGS", GCC's built-in link spec evaluates "%:include(libgomp.spec)" or "%:include(libsanitizer.spec)" and searches for spec files in "-L" and sysroot directories (including subdirectories and multilib sibling directories such as "../lib64"), as well as the working directory when "-fopenmp" or "-fopenacc" is used or when "-fsanitize=" is combined with "-static" or "-static-lib*". The go command now rejects "-L", "-isysroot", and "-Wl,-syslibroot" directories (and the working and package directories when applicable) that contain GCC spec files, and disallows "@" and "-" prefixes in "-fsanitize=" compiler flag values.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Go toolchain | <1.26.11, >=1.27.0-0 <1.27.4 | 1.26.11, 1.27.4 | |
| go: toolchain | >=1.27.0-0 <1.27.4 | 1.27.4 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in toolchain (Go), strongest first
Embed
A live severity badge for an advisory, README or ticket