CVE-2024-45339 | 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-28 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-45339 is rated Low Risk (36.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.08%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-45339

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-08 0.03% 0.08% +0.05%
2 2025-11-21 0.07% 0.03% -0.05%
3 2025-11-18 — 0.07% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-45339

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-45339

GitHub Security Advisory for CVE-2024-45339

GHSA-6wxm-mpqj-6jpf · Severity: medium · Ecosystem: go — Insecure Temporary File usage in github.com/golang/glog

OS Trackers for CVE-2024-45339

vendor priority summary link
debian not yet assigned CVE-2024-45339 not yet assigned priority: Debian including 1 source packages (golang-glog), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-45339
redhat high — https://access.redhat.com/security/cve/CVE-2024-45339
suse high — https://www.suse.com/security/cve/CVE-2024-45339/
ubuntu medium CVE-2024-45339 medium priority: Ubuntu including 1 source packages (golang-glog), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 5, not-affected 2, ignored 1, released 1. https://ubuntu.com/security/CVE-2024-45339

Affected software / configurations for CVE-2024-45339

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-45339

cvelogic Threat Intelligence