-
Notifications
You must be signed in to change notification settings - Fork 557
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
Update module github.com/hashicorp/go-retryablehttp to v0.7.7 [SECURITY] (release-2.11) #8537
Conversation
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
It's a version tagged at the same commit as the existing short SHA. Signed-off-by: Jack Baldry <[email protected]> (cherry picked from commit 70fa416)
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
414da12
to
9c1501e
Compare
* run skopeo via docker in integration tests. Signed-off-by: Peter Štibraný <[email protected]> * Use fixed version. Signed-off-by: Peter Štibraný <[email protected]> * Add /tmp volume and path to docker.sock. Signed-off-by: Peter Štibraný <[email protected]> * Only map /tmp/images. Signed-off-by: Peter Štibraný <[email protected]> --------- Signed-off-by: Peter Štibraný <[email protected]> (cherry picked from commit 24ae27e) (cherry picked from commit 27751d5)
9c1501e
to
16d4d45
Compare
* Initialize Tanka with 1.29. Signed-off-by: Peter Štibraný <[email protected]> * Update other refs. Signed-off-by: Peter Štibraný <[email protected]> --------- Signed-off-by: Peter Štibraný <[email protected]> (cherry picked from commit f62476c)
This PR contains the following updates:
v0.7.4
->v0.7.7
go-retryablehttp can leak basic auth credentials to log files
GHSA-v6v8-xj6m-xwqh
More information
Details
go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.
Severity
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
References
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Leak of sensitive information to log files in github.com/hashicorp/go-retryablehttp
GO-2024-2947
More information
Details
URLs were not sanitized when writing them to log files. This could lead to writing sensitive HTTP basic auth credentials to the log file.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Release Notes
hashicorp/go-retryablehttp (github.com/hashicorp/go-retryablehttp)
v0.7.7
Compare Source
v0.7.6
Compare Source
v0.7.5
Compare Source
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.
This PR has been generated by Mend Renovate. View repository job log here.