data/reports: update GO-2025-3372 (add GHSA)

  - data/reports/GO-2025-3372.yaml

Fixes #3425
Fixes #3372

Change-Id: Ifc802e0b7e3f14533b35b39c08851a9c936ffdba
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/645139
LUCI-TryBot-Result: Go LUCI <[email protected]>
Reviewed-by: Damien Neil <[email protected]>
Auto-Submit: Tatiana Bradley <[email protected]>

Author: tatianab

data/osv/GO-2025-3372.json

@@ -4,7 +4,8 @@
   "modified": "0001-01-01T00:00:00Z",
   "published": "0001-01-01T00:00:00Z",
   "aliases": [
-    "CVE-2024-45339"
+    "CVE-2024-45339",
+    "GHSA-6wxm-mpqj-6jpf"
   ],
   "summary": "Vulnerability when creating log files in github.com/golang/glog",
   "details": "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.",

data/reports/GO-2025-3372.yaml

@@ -74,6 +74,8 @@ description: |-
     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.
+ghsas:
+    - GHSA-6wxm-mpqj-6jpf
 credits:
     - Josh McSavaney
     - Günther Noack