CVE-2023-39348

GitHub token disclosure via forced full request logging

Published Aug 28, 2023 · Updated Sep 30, 2024

Sensitive-data exposure in affected Spinnaker releases allows attackers to obtain GitHub tokens from Echo logs during status updates. Echo's GithubConfig.githubService builder hard-codes Retrofit's FULL log level, causing authorization headers to be written instead of defaulting to BASIC. The condition exists only when GitHub Status Notifications are used; a disclosed token permits repository access within that token's assigned scope.

CVSS severity4.0
Medium
EPSS probability0.38%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive-data exposure in affected Spinnaker releases allows attackers to obtain GitHub tokens from Echo logs during status updates. Echo's GithubConfig.githubService builder hard-codes Retrofit's FULL log level, causing authorization headers to be written instead of defaulting to BASIC. The condition exists only when GitHub Status Notifications are used; a disclosed token permits repository access within that token's assigned scope.

The record

CVE
CVE-2023-39348
Published
Aug 28, 2023
Updated
Sep 30, 2024
Vendor
Spinnaker
Product
Spinnaker
Classifications
CWE-532, T1552.001
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 28, 2023CVE publishedPublication date reported by the CVE source.
  2. Sep 30, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.28.8
  2. Affected versionversion=>= 1.29.0, < 1.29.6
  3. Affected versionversion=>= 1.30.0, < 1.30.3
  4. Affected versionversion=>= 1.31.0, < 1.31.1

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

Spinnaker · Spinnakerversion=< 1.28.8; version=>= 1.29.0, < 1.29.6; version=>= 1.30.0, < 1.30.3; version=>= 1.31.0, < 1.31.1

Published CVSS scores

4.0GitHub, Inc.CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
5.3NISTCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-532Insertion of Sensitive Information into Log File
T1552.001Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo