CVE-2023-39348: 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
Other sources
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.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the impact of CVE-2023-39348?
The impact of CVE-2023-39348 is that log output when updating GitHub status is improperly set to FULL always, which could expose GitHub tokens to a log system.
How can I mitigate the impact of CVE-2023-39348?
To mitigate the impact of CVE-2023-39348, it is recommended to apply the patch and rotate the GitHub token used for GitHub status notifications.
Which versions of Spinnaker are affected by CVE-2023-39348?
The versions of Spinnaker affected by CVE-2023-39348 are 1.28.8 up to, but not including, 1.31.1.
Where can I find more information about CVE-2023-39348?
More information about CVE-2023-39348 can be found at the following references: - [GitHub Security Advisory](https://github.com/spinnaker/spinnaker/security/advisories/GHSA-rq5c-hvw6-8pr7) - [NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-39348)
What is the severity rating of CVE-2023-39348?
CVE-2023-39348 has a severity rating of 5.3 (Medium).