Improper log output when using GitHub Status Notifications in spinnaker
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-532.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| spinnaker | spinnaker | before 1.28.8; 1.29.0 to before 1.29.6; 1.30.0 to before 1.30.3; 1.31.0 to before 1.31.1 | 1.28.8, 1.29.6, 1.30.3, 1.31.1 | Patch available | CNA |
| — | github.com/spinnaker/spinnaker (Go) | all versions | — | No fix listed | GHSA-rq5c-hvw6-8pr7 |
| — | github.com/spinnaker/spinnaker (Go) | 1.29.0 and later | — | No fix listed | GHSA-rq5c-hvw6-8pr7 |
| — | github.com/spinnaker/spinnaker (Go) | 1.30.0 and later | — | No fix listed | GHSA-rq5c-hvw6-8pr7 |
| — | github.com/spinnaker/spinnaker (Go) | 1.31.0 and later | — | No fix listed | GHSA-rq5c-hvw6-8pr7 |
- spinnaker Vendorspinnaker Affected before 1.28.8; 1.29.0 to before 1.29.6; 1.30.0 to before 1.30.3; 1.31.0 to before 1.31.1 Fixed in 1.28.8, 1.29.6, 1.30.3, 1.31.1 Patch available CNA
- github.com/spinnaker/spinnaker (Go) Vendor— Affected all versions Fixed in — No fix listed GHSA-rq5c-hvw6-8pr7
- github.com/spinnaker/spinnaker (Go) Vendor— Affected 1.29.0 and later Fixed in — No fix listed GHSA-rq5c-hvw6-8pr7
- github.com/spinnaker/spinnaker (Go) Vendor— Affected 1.30.0 and later Fixed in — No fix listed GHSA-rq5c-hvw6-8pr7
- github.com/spinnaker/spinnaker (Go) Vendor— Affected 1.31.0 and later Fixed in — No fix listed GHSA-rq5c-hvw6-8pr7
Remediation
- Fix · CNA spinnaker (spinnaker) Fixed in 1.28.8, 1.29.6, 1.30.3, 1.31.1
Timeline
- 2026-10-02 Threatist record created from CVE-2023-39348
- 2026-10-03 Alias added: GHSA-rq5c-hvw6-8pr7
References
More spinnaker vulnerabilities
- TI-2021-16529 Path Traversal in spinnaker CVSS 3.1HIGH 7.1
- TI-2021-19638 Improper Access Control in spinnaker CVSS 3.1CRITICAL 10.0
- TI-2026-25122 Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling CVSS 3.1CRITICAL 10.0
- TI-2026-25113 Improper input validation in spinnaker CVSS 3.1CRITICAL 10.0
- TI-2026-32679 Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types CVSS 3.1HIGH 8.8
- TI-2026-39859 Spinnaker: Improper yaml processing on kustomize bake operations CVSS 3.1HIGH 7.5
Sources
- CVE-2023-39348 · CVE Program
- CVE-2023-39348 · NVD
- FIRST EPSS
- GHSA-rq5c-hvw6-8pr7 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences