Improper log output when using GitHub Status Notifications in spinnaker

TRUNG BÌNH 5.3CVE-2023-39348 · GHSA-rq5c-hvw6-8pr7 · Công bố 28/08/2023 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2023-39348 là lỗ hổng mức TRUNG BÌNH (CVSS 5.3) ảnh hưởng github.com/spinnaker/spinnaker, spinnaker (linuxfoundation).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.38%, cao hơn 32.1% các lỗ hổng khác.
Cách xử lý: cập nhật lên 1.29.6, 1.30.3, 1.28.8 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
github.com/spinnaker/spinnaker Go	`≥ 1.29.0≥ 1.30.0≥ 1.31.0mọi phiên bản`	Chưa có bản vá
spinnaker linuxfoundation	`= 1.30.0≥ 1.29.0, < 1.29.6≥ 1.30.0, < 1.30.3< 1.28.8`	`1.29.61.30.31.28.8`

Mô tả

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

Mô tả của 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.