Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-rq5c-hvw6-8pr7: Improper log output when using GitHub Status Notifications in spinnaker

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

ghsa
#git#perl
  1. GitHub Advisory Database
  2. GitHub Reviewed
  3. CVE-2023-39348

Improper log output when using GitHub Status Notifications in spinnaker

Moderate severity GitHub Reviewed Published Aug 28, 2023 in spinnaker/spinnaker

Package

gomod github.com/spinnaker/spinnaker (Go)

Affected versions

< 1.28.8

>= 1.29.0, < 1.29.6

>= 1.30.0, < 1.30.3

>= 1.31.0, < 1.31.1

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. spinnaker/echo#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

  • GHSA-rq5c-hvw6-8pr7
  • https://nvd.nist.gov/vuln/detail/CVE-2023-39348
  • spinnaker/echo#1316

Published to the GitHub Advisory Database

Aug 29, 2023

Related news

CVE-2023-39348: fix(gha): Fix github status log and add tests by jasonmcintosh · Pull Request #1316 · spinnaker/echo

Spinnaker is an open source, multi-cloud continuous delivery platform. 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. This only affects users of GitHub Status Notifications. This issue has been addressed in pull request 1316. Users are advised to upgrade. Users unable to upgrade should disable GH Status Notifications, Filter their logs for Echo log data and use read-only tokens that are limited in scope.