VYPR

Desktop

by Docker

Source repositories

CVEs (34)

  • CVE-2022-34292HigApr 27, 2023
    risk 0.46cvss 7.1epss 0.00

    Docker Desktop for Windows before 4.6.0 allows attackers to overwrite any file through a symlink attack on the hyperv/create dockerBackendV2 API by controlling the DataFolder parameter for DockerDesktop.vhdx, a similar issue to CVE-2022-31647.

  • CVE-2022-31647HigApr 27, 2023
    risk 0.46cvss 7.1epss 0.00

    Docker Desktop before 4.6.0 on Windows allows attackers to delete any file through the hyperv/destroy dockerBackendV2 API via a symlink in the DataFolder parameter, a different vulnerability than CVE-2022-26659.

  • CVE-2023-0629HigMar 13, 2023
    risk 0.46cvss 7.1epss 0.00

    Docker Desktop before 4.17.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions by setting the Docker host to docker.raw.sock, or npipe:////.pipe/docker_engine_linux on Windows, via the -H (--host) CLI flag or the DOCKER_HOST environment…

  • CVE-2022-26659HigMar 25, 2022
    risk 0.46cvss 7.1epss 0.00

    Docker Desktop installer on Windows in versions before 4.6.0 allows an attacker to overwrite any administrator writable files by creating a symlink in place of where the installer writes its log file. Starting from version 4.6.0, the Docker Desktop installer, when run elevated,…

  • CVE-2023-0627MedSep 25, 2023
    risk 0.44cvss 6.7epss 0.00

    Docker Desktop 4.11.x allows --no-windows-containers flag bypass via IPC response spoofing which may lead to Local Privilege Escalation (LPE).This issue affects Docker Desktop: 4.11.X.

  • CVE-2020-10665MedMar 18, 2020
    risk 0.44cvss 6.7epss 0.01

    Docker Desktop allows local privilege escalation to NT AUTHORITY\SYSTEM because it mishandles the collection of diagnostics with Administrator privileges, leading to arbitrary DACL permissions overwrites and arbitrary file writes. This affects Docker Desktop Enterprise before…

  • CVE-2022-38730MedApr 27, 2023
    risk 0.41cvss 6.3epss 0.00

    Docker Desktop for Windows before 4.6 allows attackers to overwrite any file through the windowscontainers/start dockerBackendV2 API by controlling the data-root field inside the DaemonJSON field in the WindowsContainerStartRequest class. This allows exploiting a symlink…

  • CVE-2024-5652MedJul 9, 2024
    risk 0.40cvss 6.1epss 0.00

    In Docker Desktop on Windows before v4.31.0 allows a user in the docker-users group to cause a Windows Denial-of-Service through the exec-path Docker daemon config option in Windows containers mode.

  • CVE-2023-0628MedMar 13, 2023
    risk 0.40cvss 6.1epss 0.00

    Docker Desktop before 4.17.0 allows an attacker to execute an arbitrary command inside a Dev Environments container during initialization by tricking a user to open a crafted malicious docker-desktop:// URL.

  • CVE-2023-1802MedApr 6, 2023
    risk 0.38cvss 5.9epss 0.01

    In Docker Desktop 4.17.x the Artifactory Integration falls back to sending registry credentials over plain HTTP if the HTTPS health check has failed. A targeted network sniffing attack can lead to a disclosure of sensitive information. Only users who have Access Experimental…

  • CVE-2021-45449MedJan 12, 2022
    risk 0.36cvss 5.5epss 0.00

    Docker Desktop version 4.3.0 and 4.3.1 has a bug that may log sensitive information (access token or password) on the user's machine during login. This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1. Gaining access…

  • CVE-2022-23774MedFeb 1, 2022
    risk 0.35cvss 5.3epss 0.01

    Docker Desktop before 4.4.4 on Windows allows attackers to move arbitrary files.

  • CVE-2025-1696MedMar 6, 2025
    risk 0.34cvss epss 0.00

    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…

  • CVE-2025-4095MedApr 29, 2025
    risk 0.28cvss epss 0.00

    Registry Access Management (RAM) is a security feature allowing administrators to restrict access for their developers to only allowed registries. When a MacOS configuration profile is used to enforce organization sign-in, the RAM policies are not being applied, which would…

Page 2 of 2