CVE-2023-39348

Improper log output when using GitHub Status Notifications in spinnaker

MEDIUM

5.3

CVSS Score

Published: August 28, 2023 at 07:47 PM UTC

Updated: June 17, 2026 at 06:12 AM UTC

2 products affected across 2 vendorsSpinnakerSpinnaker

Using spinnaker by spinnaker?

Get instant alerts when new vulnerabilities affect spinnaker - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.3

Exploit prediction

EPSS 0.4%

SSVC

No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Spinnaker · Linuxfoundation

95%

v < 1.28.81.29.0 ≤ v < 1.29.61.30.0 ≤ v < 1.30.31.30.0

Affected range stops below 1.28.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.29.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.30.3, so it looks safe — our inference, not a vendor statement

Spinnaker · Spinnaker

60%

v < 1.28.8v < 1.29.6v < 1.30.3v < 1.31.1

Affected range stops below 1.28.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.29.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.30.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.31.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_MISCPatch

Source: [email protected]

https://github.com/spinnaker/echo/pull/1316

x_refsource_CONFIRMVendor Advisory

Source: [email protected]

https://github.com/spinnaker/spinnaker/security/advisories/GHSA-rq5c-hvw6-8pr7

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUM[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: LOW
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card