In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsThere is no fixed version for Debian:unstable
golang-glog
.
Note: Versions mentioned in the description apply only to the upstream golang-glog
package and not the golang-glog
package as distributed by Debian
.
See How to fix?
for Debian:unstable
relevant fixed versions and status.
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.