Skip to content
Fencer Intel
low —

GHSA-xr7q-jx4m-x55m json

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

published 2y ago modified 2mo ago also GO-2024-2978

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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.

Patch / fix

  • go google.golang.org/grpc 1.64.1

Is GHSA-xr7q-jx4m-x55m in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go google.golang.org/grpc
>=1.64.0, <1.64.1
1.64.1

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.