Docker Desktop logs can expose stored third-party credentials
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Docker | Docker Desktop | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Docker | Desktop |
|
Vendor Solution
Upgrade to Docker Desktop 4.97.0 or later.
Vendor Workaround
Restrict access to existing local application logs and diagnostics bundles that may contain credentials, and revoke or rotate exposed credentials.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.107% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Docker Desktop logs can expose stored third-party credentials | |
| First Time appeared |
Docker
Docker desktop |
|
| Weaknesses | CWE-532 | |
| CPEs | cpe:2.3:a:docker:desktop:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Docker
Docker desktop |
|
| References |
| |
| Metrics |
cvssV4_0
|