Skip to content
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

chore(deps): update module github.com/hashicorp/go-retryablehttp to v0.7.7 [security] (release-2.9.x) - abandoned #13337

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 27, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/hashicorp/go-retryablehttp v0.7.2 -> v0.7.7 age adoption passing confidence

go-retryablehttp can leak basic auth credentials to log files

CVE-2024-6104 / GHSA-v6v8-xj6m-xwqh / GO-2024-2947

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 Score: 6.0 / 10 (Medium)
  • Vector String: 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

CVE-2024-6104 / GHSA-v6v8-xj6m-xwqh / 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

v0.7.4

Compare Source

v0.7.3

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Jun 27, 2024

ℹ 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):

  • 4 additional dependencies were updated

Details:

Package Change
github.com/fatih/color v1.15.0 -> v1.16.0
golang.org/x/sys v0.18.0 -> v0.20.0
github.com/hashicorp/go-hclog v1.4.0 -> v1.6.3
github.com/mattn/go-isatty v0.0.17 -> v0.0.20

@renovate renovate bot requested a review from a team as a code owner June 27, 2024 07:29
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 27, 2024
@renovate renovate bot force-pushed the deps-update/release-2.9.x-go-github.com/hashicorp/go-retryablehttp-vulnerability branch from 77577b0 to d051b39 Compare July 1, 2024 12:31
@renovate renovate bot changed the title chore(deps): update module github.com/hashicorp/go-retryablehttp to v0.7.7 [security] (release-2.9.x) chore(deps): update module github.com/hashicorp/go-retryablehttp to v0.7.7 [security] (release-2.9.x) - abandoned Aug 6, 2024
Copy link
Contributor Author

renovate bot commented Aug 6, 2024

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security dependencies Pull requests that update a dependency file size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant