CVE-2024-45339
When logs are written to a widely-writable directory (the default), …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/golang/glog/pull/74
- github.com/golang/glog/pull/74/commits/b8741656e406e66d6992bc2c9575e460ecaa0ec2
- groups.google.com/g/golang-announce/c/H-Q4ouHWyKs
- owasp.org/www-community/vulnerabilities/Insecure_Temporary_File
- pkg.go.dev/vuln/GO-2025-3372
- lists.debian.org/debian-lts-announce/2025/02/msg00019.html
- nvd.nist.gov/vuln/detail/CVE-2024-45339
- github.com/advisories/GHSA-6wxm-mpqj-6jpf
- nvd.nist.gov/vuln/detail/CVE-2024-45339
- cve.org/CVERecord?id=CVE-2024-45339
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.