Medium, CVSS 4.1GoPublished
Insecure Temporary File usage in github.com/golang/glog
CVE-2024-45339 · GHSA-6wxm-mpqj-6jpf
- Affected
- Go github.com/golang/glog < 1.2.4
- Fixed in
- 1.2.4· Vendor fix available
- Issue
- When logs are written to a widely-writable directory (the default), an unprivileged attacker may predict a privileged process's log file path and pre-create a symbolic link to a sensitive file in its place. When that privileged process runs, it will follow the planted symlink and overwrite that sensitive file. To fix that, glog now causes the program to exit (with status code 2) when it finds that the configured log file already exists.
Recommended action: Upgrade to 1.2.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.