CVE-2023-39348
Improper log output when using GitHub Status Notifications in spinnaker
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.
Attack profile
How easy it is to exploit
- Attack vector
- Physical
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
Improper log output when using GitHub Status Notifications in spinnaker
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.
- Record
CVE-2023-39348- CVSS 3.1
- 4.0 Medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - Weakness
- CWE-532
- Updated
- 2026-11-02
EUVDEUVD-2023-2349
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.
- Record
EUVD-2023-2349- CVSS 3.1
- 4.0 Medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-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
- Record
GHSA-rq5c-hvw6-8pr7- CVSS 3.1
- 4.0 Medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - Weakness
- CWE-532
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2023-39348- CVSS 3.1
- 4.0 Medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-532
- Updated
- 2026-11-02
OSVGHSA-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
- Record
GHSA-rq5c-hvw6-8pr7- CVSS 3.1
- 4.0 Medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - Weakness
- CWE-532
- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/spinnaker/spinnakerGo |
before 1.28.8 | 1.28.8 |
github.com/spinnaker/spinnakerGo |
1.29.0 up to 1.29.6 | 1.29.6 |
github.com/spinnaker/spinnakerGo |
1.30.0 up to 1.30.3 | 1.30.3 |
github.com/spinnaker/spinnakerGo |
1.31.0 up to 1.31.1 | 1.31.1 |
github.com/spinnaker/spinnakerGo |
All versions | None known |
github.com/spinnaker/spinnakerGo |
1.29.0 and later | None known |
github.com/spinnaker/spinnakerGo |
1.30.0 and later | None known |
github.com/spinnaker/spinnakerGo |
1.31.0 and later | None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases, published | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2023-39348 is a medium vulnerability (CVSS 4.0) in Linuxfoundation Spinnaker, published August 28, 2023. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.38%, the 32nd percentile. Fixed in github.com/spinnaker/spinnaker 1.28.8.