CVE-2025-1696: Exposure of Proxy Credentials in Docker Desktop Logs
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-1696?
CVE-2025-1696 is considered a medium severity vulnerability due to the risk of sensitive information disclosure.
How can I mitigate CVE-2025-1696?
To mitigate CVE-2025-1696, upgrade Docker Desktop to version 4.39.0 or later to prevent sensitive data from being logged.
What information is at risk in CVE-2025-1696?
CVE-2025-1696 could lead to the exposure of proxy configuration data, which may include sensitive details like authentication tokens.
What versions of Docker Desktop are affected by CVE-2025-1696?
Docker Desktop versions prior to 4.39.0 are affected by CVE-2025-1696.
Is there any remediation for CVE-2025-1696 besides upgrading?
While upgrading is the primary remediation, ensure that log files are monitored and managed securely to prevent data exposure.