GHSA-rq5c-hvw6-8pr7
Improper log output when using GitHub Status Notifications in spinnaker
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Go | github.com/spinnaker/spinnaker | < 1.28.8 | no fix listed |
| Go | github.com/spinnaker/spinnaker | < 1.29.6 | no fix listed |
| Go | github.com/spinnaker/spinnaker | < 1.30.3 | no fix listed |
| Go | github.com/spinnaker/spinnaker | < 1.31.1 | no fix listed |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
ONLY IMPACTS those use GitHub Status Notifications
Log output when updating GitHub status is improperly set to FULL always. It's recommended to apply the patch and rotate the GitHub token used for github status notifications. Given that this would output github tokens to a log system, the risk is slightly higher than a "low" since token exposure could grant elevated access to repositories outside of control. If using READ restricted tokens, the exposure is such that the token itself could be used to access resources otherwise restricted from reads.
### Patches
Patch is in progress. https://github.com/spinnaker/echo/pull/1316
### Workarounds
Disable GH Status Notifications. Filter your logs for Echo log data. Use read-only tokens that are limited in scope.
### References
sig-security in slack: https://spinnakerteam.slack.com/archives/CFN8F5UR2
References
External links from the advisory. They lead to third-party sites.