CVE-2023-39348 is a medium-severity (CVSS 4) CWE-532 vulnerability in github.com/spinnaker/spinnaker. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Improper log output when using GitHub Status Notifications in spinnaker
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-39348.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/spinnaker/spinnaker🐹github.com/spinnaker/spinnaker🐹github.com/spinnaker/spinnaker🐹github.com/spinnaker/spinnakerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/spinnaker/spinnaker | all versions | No fix |
| 🐹Go | github.com/spinnaker/spinnaker | ≥ 1.29.0 | No fix |
| 🐹Go | github.com/spinnaker/spinnaker | ≥ 1.30.0 | No fix |
| 🐹Go | github.com/spinnaker/spinnaker | ≥ 1.31.0 | No fix |
Affected Products
spinnakerlinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/spinnaker/spinnaker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/spinnaker/spinnaker for CVE-2023-39348. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2023-39348 in your dependencies?
Find it across Go, including transitive dependencies.