# CVE-2023-39348: Improper log output when using GitHub Status Notifications in spinnaker > Spinnaker improperly logs GitHub tokens, allowing attackers with log access to steal credentials and access repositories. - **Severity:** Medium 4.0 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 28 Aug 2023 - **Updated:** 30 Sep 2024 - **Also known as:** GHSA-rq5c-hvw6-8pr7 ## What is CVE-2023-39348? CVE-2023-39348 is a medium-severity vulnerability in spinnaker, published on 28 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-532 (Insertion of Sensitive Information into Log File) ## Which versions are affected by CVE-2023-39348? 8 open source packages ship an affected version, including github.com/spinnaker/spinnaker. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/spinnaker/spinnaker` | Go | All versions | None | | `github.com/spinnaker/spinnaker` | Go | All versions | None | | `github.com/spinnaker/spinnaker` | Go | From 1.29.0 | None | | `github.com/spinnaker/spinnaker` | Go | From 1.29.0 | None | | `github.com/spinnaker/spinnaker` | Go | From 1.30.0 | None | | `github.com/spinnaker/spinnaker` | Go | From 1.30.0 | None | | `github.com/spinnaker/spinnaker` | Go | From 1.31.0 | None | | `github.com/spinnaker/spinnaker` | Go | From 1.31.0 | None | Products: Linuxfoundation Spinnaker. ## How do I fix CVE-2023-39348? No fix has been published for CVE-2023-39348 yet. Limit exposure of the affected software until one is available. ## Is CVE-2023-39348 being exploited? There is no known exploitation of CVE-2023-39348 in the wild and no public exploit code. ## Other vulnerabilities in spinnaker - [CVE-2026-32604](https://insights.sbomify.com/CVE-2026-32604/): Spinnaker: RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths (critical 10.0) - [CVE-2026-32613](https://insights.sbomify.com/CVE-2026-32613/): Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling (critical 10.0) - [CVE-2021-43832](https://insights.sbomify.com/CVE-2021-43832/): Improper Access Control in spinnaker (critical 10.0) - [CVE-2026-44795](https://insights.sbomify.com/CVE-2026-44795/): Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types (high 8.8) - [CVE-2020-9301](https://insights.sbomify.com/CVE-2020-9301/): Code injection in Netflix Spinnaker (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-39348 and fix it if it is affected. What it is: CVE-2023-39348 is a medium-severity vulnerability in spinnaker, published on 28 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-39348 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/spinnaker/spinnaker (Go): affected all versions; no fix listed - github.com/spinnaker/spinnaker (Go): affected all versions; no fix listed - github.com/spinnaker/spinnaker (Go): affected from 1.29.0; no fix listed - github.com/spinnaker/spinnaker (Go): affected from 1.29.0; no fix listed - github.com/spinnaker/spinnaker (Go): affected from 1.30.0; no fix listed - github.com/spinnaker/spinnaker (Go): affected from 1.30.0; no fix listed - github.com/spinnaker/spinnaker (Go): affected from 1.31.0; no fix listed - github.com/spinnaker/spinnaker (Go): affected from 1.31.0; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-39348/ (Markdown: https://insights.sbomify.com/CVE-2023-39348/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-39348 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-39348 - OSV: https://osv.dev/vulnerability/CVE-2023-39348 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-39348/ Summaries are generated and may contain mistakes; the official description above is the record.