ssp-operator
ssp-operator copied to clipboard
chore(deps): update module github.com/golang/glog to v1.2.4 [security] (release-v0.16)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| github.com/golang/glog | indirect | minor | v1.0.0 -> v1.2.4 |
Insecure Temporary File usage in github.com/golang/glog
CVE-2024-45339 / GHSA-6wxm-mpqj-6jpf / GO-2025-3372
More information
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.
Severity
- CVSS Score: 7.1 / 10 (High)
- Vector String:
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-45339
- https://github.com/golang/glog/pull/74
- https://github.com/golang/glog/pull/74/commits/b8741656e406e66d6992bc2c9575e460ecaa0ec2
- https://github.com/golang/glog
- https://groups.google.com/g/golang-announce/c/H-Q4ouHWyKs
- https://lists.debian.org/debian-lts-announce/2025/02/msg00019.html
- https://owasp.org/www-community/vulnerabilities/Insecure_Temporary_File
- https://pkg.go.dev/vuln/GO-2025-3372
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Vulnerability when creating log files in github.com/golang/glog
CVE-2024-45339 / GHSA-6wxm-mpqj-6jpf / GO-2025-3372
More information
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.
Severity
Unknown
References
- https://github.com/golang/glog/pull/74/commits/b8741656e406e66d6992bc2c9575e460ecaa0ec2
- https://github.com/golang/glog/pull/74
- https://groups.google.com/g/golang-announce/c/H-Q4ouHWyKs
- https://owasp.org/www-community/vulnerabilities/Insecure_Temporary_File
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Release Notes
golang/glog (github.com/golang/glog)
v1.2.4
What's Changed
- Fail if log file already exists by @chressie in https://github.com/golang/glog/pull/74:
- glog: Don't try to create/rotate a given syncBuffer twice in the same second
- glog: introduce createInDir function as in internal version
- glog: have createInDir fail if the file already exists
Full Changelog: https://github.com/golang/glog/compare/v1.2.3...v1.2.4
v1.2.3
What's Changed
- glog: check that stderr is valid before using it by default by @chressie in https://github.com/golang/glog/pull/72
- glog: fix typo by @chressie in https://github.com/golang/glog/pull/73
Full Changelog: https://github.com/golang/glog/compare/v1.2.2...v1.2.3
v1.2.2
What's Changed
- glog: avoid calling user.Current() on windows by @bentekkie in https://github.com/golang/glog/pull/69
Full Changelog: https://github.com/golang/glog/compare/v1.2.1...v1.2.2
v1.2.1
What's Changed
- glog: don't hold mutex when sync'ing by @chressie in https://github.com/golang/glog/pull/68
Full Changelog: https://github.com/golang/glog/compare/v1.2.0...v1.2.1
v1.2.0
What's Changed
- glog: add context variants and logsink tests by @chressie in https://github.com/golang/glog/pull/66
Full Changelog: https://github.com/golang/glog/compare/v1.1.2...v1.2.0
v1.1.2
Bugfix release.
What's Changed
- glog: populate symlinks -log_link directory by @chressie in https://github.com/golang/glog/pull/64
Full Changelog: https://github.com/golang/glog/compare/v1.1.1...v1.1.2
v1.1.1
Bugfixes since the larger v1.1.0, which have been addressed.
v1.1.0
Tagging v1.1.0 after syncing glog with internal changes
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):
- 1 additional dependency was updated
Details:
| Package | Change |
|---|---|
github.com/google/go-cmp |
v0.5.9 -> v0.6.0 |
/retest
/retest
Upstream CI wants to run on unsupported OCP version. Maybe cluster cannot be created. I will update CI config.
CI update PR: https://github.com/openshift/release/pull/69701
CI change has been merged.
/retest
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: 0xFelix Once this PR has been reviewed and has the lgtm label, please assign ksimon1 for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest
@redhat-renovate-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-functests | 4284ce3131c0bc82c6edae509943966ab2bf31e4 | link | true | /test e2e-functests |
| ci/prow/e2e-upgrade-functests | 4284ce3131c0bc82c6edae509943966ab2bf31e4 | link | true | /test e2e-upgrade-functests |
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.
