dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-1696

MEDIUM · 5.2 CVSS v4.0 Published 2025-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
54/100
Remediation priority · Moderate
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability exists in Docker Desktop prior to version 4.39.0 that could lead to the unintentional disclosure of sensitive information via application logs. In affected versions, proxy configuration data—potentially including sensitive details—was written to log files in clear text whenever an HTTP GET request was made through a proxy. An attacker with read access to these logs could obtain the proxy information and leverage it for further attacks or unauthorized access. Starting with version 4.39.0, Docker Desktop no longer logs the proxy string, thereby mitigating this risk.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Docker Desktop versions prior to 4.39.0 write proxy configuration data (potentially including credentials) to application log files in clear text during HTTP GET requests made through a proxy. An attacker with read access to these logs can obtain the proxy credentials and use them for further attacks or unauthorized network access.

MitigationUpgrade Docker Desktop to version 4.39.0 or later, which no longer logs the proxy string. Also review existing log files for any inadvertent proxy credential exposure and rotate those credentials if found.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Docker Desktop version
    Open Docker Desktop and navigate to the About section, or run 'docker --version' and 'docker compose version' from the CLI to confirm the installed version.
    Affected if The installed version is lower than 4.39.0 (for example, 4.38.0, 4.37.0, etc.)
  2. Confirm proxy configuration exists
    Inspect Docker Desktop proxy settings: go to Settings > Resources > Proxies, or check the Docker Desktop configuration file for any proxy URL that includes authentication (such as http://user:password@proxy:port or similar patterns).
    Affected if A proxy is configured with embedded credentials (username and password) in the proxy URL or settings.
  3. Locate Docker Desktop log files
    Access the Docker Desktop log directory. On Windows this is typically %LOCALAPPDATA%\Docker\log\, on Mac it is ~/Library/Logs/Docker/. Identify all log files such as viewer.log, console.log, or similar application logs.
    Affected if Log files exist and were created or modified while using Docker Desktop versions prior to 4.39.0 with an authenticated proxy configured.
  4. Search logs for proxy credentials
    Open the log files using a text editor or search utility and look for strings containing the proxy URL with username and password in clear text. Search for patterns like 'http://', 'proxy', and credential separators (@, :, //).
    Affected if The log files contain the proxy username and password in clear text (for example, lines showing http://myuser:mypassword@proxyhost:8080 or similar credential strings).

A user is affected if they run Docker Desktop versions before 4.39.0, have a proxy with authentication configured, and their log files contain proxy credentials in clear text.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Docker Desktop to version 4.39.0 or later, which no longer logs the proxy string. Also review existing log files for any inadvertent proxy credential exposure and rotate those credentials if found.

Recommended fix High confidence

Docker Desktop 4.39.0 or later

  1. 1. Check the current Docker Desktop version by clicking the Docker icon in the system tray and selecting 'About Docker Desktop'
  2. 2. If the version is earlier than 4.39.0, download Docker Desktop version 4.39.0 or later from the official Docker website
  3. 3. Uninstall the current Docker Desktop version
  4. 4. Install the downloaded Docker Desktop 4.39.0 or later
  5. 5. Restart the system and verify the new version by checking 'About Docker Desktop'

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1696 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data