What is CVE-2023-39348?

CVE-2023-39348 is a medium-severity security vulnerability in github.com/spinnaker/spinnaker (go), affecting versions < 1.28.8. No fixed version is listed yet.

How severe is CVE-2023-39348?

CVE-2023-39348 has a CVSS score of 4.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/spinnaker/spinnaker are affected by CVE-2023-39348?

github.com/spinnaker/spinnaker (go) versions < 1.28.8 is affected.

Is there a fix for CVE-2023-39348?

No fixed version is listed for CVE-2023-39348 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2023-39348 exploitable, and should I be worried?

Whether CVE-2023-39348 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-39348 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-39348 in github.com/spinnaker/spinnaker

Q: How severe is CVE-2023-39348?

CVE-2023-39348 has a CVSS score of 4.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/spinnaker/spinnaker are affected by CVE-2023-39348?

github.com/spinnaker/spinnaker (go) versions < 1.28.8 is affected.

Q: Is there a fix for CVE-2023-39348?

No fixed version is listed for CVE-2023-39348 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2023-39348 exploitable, and should I be worried?

Whether CVE-2023-39348 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-39348 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Summary

Improper log output when using GitHub Status Notifications in spinnaker

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

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.

CVE-2023-39348 has a CVSS score of 4.0 (Medium). The vector is requires physical access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

github.com/spinnaker/spinnaker (< 1.28.8) github.com/spinnaker/spinnaker (>= 1.29.0, < 1.29.6) github.com/spinnaker/spinnaker (>= 1.30.0, < 1.30.3) github.com/spinnaker/spinnaker (>= 1.31.0, < 1.31.1)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Patch is in progress. https://github.com/spinnaker/echo/pull/1316

Frequently Asked Questions

What is CVE-2023-39348? CVE-2023-39348 is a medium-severity security vulnerability in github.com/spinnaker/spinnaker (go), affecting versions < 1.28.8. No fixed version is listed yet.
How severe is CVE-2023-39348? CVE-2023-39348 has a CVSS score of 4.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/spinnaker/spinnaker are affected by CVE-2023-39348? github.com/spinnaker/spinnaker (go) versions < 1.28.8 is affected.
Is there a fix for CVE-2023-39348? No fixed version is listed for CVE-2023-39348 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2023-39348 exploitable, and should I be worried? Whether CVE-2023-39348 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-39348 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.