Bug 2342463 (CVE-2024-45339)

Summary: CVE-2024-45339 github.com/golang/glog: Vulnerability when creating log files in github.com/golang/glog
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: aarif, adudiak, agarcial, ahrabovs, aoconnor, aprice, asegurap, aucunnin, bdettelb, bkabrda, brainfor, caswilli, ckandaga, cmah, crizzo, dfreiber, dkuc, doconnor, drow, fjansen, jburrell, jcantril, jdobes, jeder, jforrest, jkoehler, jmitchel, jsamir, jsherril, jtanner, jvasik, kaycoth, kgaikwad, kshier, lball, ldai, ljawale, lphiri, lsharar, lucarval, luizcosta, mpierce, mstoklus, ngough, nweather, oezr, omaciel, orabin, periklis, psegedy, pvasanth, rblanco, rbobbitt, rochandr, rojacob, stcannon, sthirugn, teagle, veshanka, vkrizan, vkumar, vmugicag, yguenane, zkayyali
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in glog, a logging library. This vulnerability allows an unprivileged attacker to overwrite sensitive files via a symbolic link planted in a widely writable directory, exploiting the log file path predictability.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2342517, 2342518, 2342528, 2342529, 2342530, 2342531, 2342532, 2342533, 2342534, 2342535, 2342536, 2342519, 2342520, 2342521, 2342522, 2342523, 2342524, 2342525, 2342526, 2342527, 2361093    
Bug Blocks:    

Description OSIDB Bzimport 2025-01-28 02:01:13 UTC 
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.