Github.Com/Golang/Glog
Approved changes feed: RSS · Atom
cpe:2.3:a:github.com/golang/glog:github.com/golang/glog:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Github.Com/Golang/Glog (729c7dfa-231b-51b2-989d-5cc8bb782ab3) |
|---|---|
| Product | Github.Com/Golang/Glog (4eeab02f-7f06-5730-b0ac-fb6f087b82a5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-45339 |
vulnerable | 2026-06-08 06:48:05.938016 |
Vulnerability when creating log files in github.com/golang/glog
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.
Published: 2025-01-28T01:03:24.105Z
Updated: 2026-04-30T03:56:03.352Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.