Local file overwrite via predictable temporary path
Published Jul 9, 2021 · Updated Aug 6, 2024
Insecure temporary-file handling in Go before 1.0.2 allows local users to overwrite files during debug/gosym tests on shared systems. dotest in src/pkg/debug/gosym/pclntab_test.go passes the fixed /tmp/pclinetest path to shell-invoked assembler and linker commands, allowing precreated links to redirect their outputs. Exploitation requires another user to run all.bash on a shared Unix host, and the write occurs with that user's filesystem permissions.
Summary
What happened
Insecure temporary-file handling in Go before 1.0.2 allows local users to overwrite files during debug/gosym tests on shared systems. dotest in src/pkg/debug/gosym/pclntab_test.go passes the fixed /tmp/pclinetest path to shell-invoked assembler and linker commands, allowing precreated links to redirect their outputs. Exploitation requires another user to run all.bash on a shared Unix host, and the write occurs with that user's filesystem permissions.
The record
- CVE
- CVE-2012-2666
- Published
- Jul 9, 2021
- Updated
- Aug 6, 2024
- Vendor
- The Go Project
- Product
- Go
- Classifications
- CWE-377, CAPEC-149, T1574
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record 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=go/golang 1.0.2
What conditions does exploitation require?
What is affected?
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