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

fix(deps): update module google.golang.org/grpc to v1.64.1 [security] - autoclosed #80

Conversation

SatisfactoryModdingBot
Copy link
Contributor

@SatisfactoryModdingBot SatisfactoryModdingBot commented Jul 26, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
google.golang.org/grpc v1.64.0 -> v1.64.1 age adoption passing confidence

Private tokens could appear in logs if context containing gRPC metadata is logged in github.com/grpc/grpc-go

GHSA-xr7q-jx4m-x55m / GO-2024-2978

More information

Details

Impact

This issue represents a potential PII concern. If applications were printing or logging a context containing gRPC metadata, the affected versions will contain all the metadata, which may include private information.

Patches

The issue first appeared in 1.64.0 and is patched in 1.64.1 and 1.65.0

Workarounds

If using an affected version and upgrading is not possible, ensuring you do not log or print contexts will avoid the problem.

Severity

Low

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Private tokens could appear in logs if context containing gRPC metadata is logged in google.golang.org/grpc

GHSA-xr7q-jx4m-x55m / GO-2024-2978

More information

Details

If applications print or log a context containing gRPC metadata, the output will contain all the metadata, which may include private information. This represents a potential PII concern.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Release Notes

grpc/grpc-go (google.golang.org/grpc)

v1.64.1: Release 1.64.1

Compare Source

Dependencies


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.

Copy link

codecov bot commented Jul 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 20.23%. Comparing base (a0847a4) to head (4b0ab53).
Report is 6 commits behind head on staging.

Additional details and impacted files
@@           Coverage Diff            @@
##           staging      #80   +/-   ##
========================================
  Coverage    20.23%   20.23%           
========================================
  Files          233      233           
  Lines        57381    57381           
========================================
  Hits         11611    11611           
  Misses       43257    43257           
  Partials      2513     2513           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@SatisfactoryModdingBot SatisfactoryModdingBot force-pushed the renovate/go-google.golang.org-grpc-vulnerability branch 4 times, most recently from 1adcf83 to de90cb7 Compare August 14, 2024 12:36
@SatisfactoryModdingBot SatisfactoryModdingBot force-pushed the renovate/go-google.golang.org-grpc-vulnerability branch from de90cb7 to 4b0ab53 Compare August 20, 2024 12:36
@SatisfactoryModdingBot SatisfactoryModdingBot changed the title fix(deps): update module google.golang.org/grpc to v1.64.1 [security] fix(deps): update module google.golang.org/grpc to v1.64.1 [security] - autoclosed Aug 27, 2024
@SatisfactoryModdingBot SatisfactoryModdingBot deleted the renovate/go-google.golang.org-grpc-vulnerability branch August 27, 2024 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants