-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): update module github.com/golang/glog to v1.2.4 [security] #38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate-sh-app
wants to merge
1
commit into
main
Choose a base branch
from
renovate/go-github.com-golang-glog-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
chore(deps): update module github.com/golang/glog to v1.2.4 [security] #38
renovate-sh-app
wants to merge
1
commit into
main
from
renovate/go-github.com-golang-glog-vulnerability
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| datasource | package | from | to | | ---------- | ---------------------- | ------ | ------ | | go | github.com/golang/glog | v1.0.0 | v1.2.4 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
|
😢 zizmor failed with exit code 14. Expand for full output |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.0.0→v1.2.4Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2024-45339
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.
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:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:UReferences
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
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.4Compare Source
What's Changed
Full Changelog: golang/glog@v1.2.3...v1.2.4
v1.2.3Compare Source
What's Changed
Full Changelog: golang/glog@v1.2.2...v1.2.3
v1.2.2Compare Source
What's Changed
Full Changelog: golang/glog@v1.2.1...v1.2.2
v1.2.1Compare Source
What's Changed
Full Changelog: golang/glog@v1.2.0...v1.2.1
v1.2.0Compare Source
What's Changed
Full Changelog: golang/glog@v1.1.2...v1.2.0
v1.1.2Compare Source
Bugfix release.
What's Changed
Full Changelog: golang/glog@v1.1.1...v1.1.2
v1.1.1Compare Source
Bugfixes since the larger v1.1.0, which have been addressed.
v1.1.0Compare Source
Tagging v1.1.0 after syncing glog with internal changes
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.