Docker Desktop logs can expose stored third-party credentials
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.97.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Docker Desktop, the desktop application for running Docker containers on Windows and macOS, can write third-party API keys and OAuth access tokens in plain text to its local logs and diagnostic bundles. Anyone who can read those files on the affected computer could obtain those credentials.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Docker Desktop before version 4.97.0 could write third-party API keys and OAuth access tokens in cleartext to local application logs and diagnostics bundles due to insufficient IPC payload redaction. An attacker with read access to these files could obtain the credentials. These OAuth tokens are not Docker account tokens. Docker Desktop 4.94.0 and 4.95.0 addressed the known logging paths, but logs containing credentials can remain after upgrading. Docker Desktop 4.97.0 fixes the issue and includes cleanup of existing host logs and crash dumps.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Docker Docker Desktop
From 4.39.0 · fixed in 4.97.0