# it only took 2 lines of code... Source: https://www.youtube.com/watch?v=QgVR1dxy6zk Recap page: https://rapidrecap.app/video/QgVR1dxy6zk Generated: 2025-08-29T15:32:26.544+00:00 --- ## Quick Overview A critical Docker Desktop vulnerability (CVE-2025-9074) allowed full container escape on Windows by exploiting an unauthenticated API endpoint, enabling attackers to gain access to the host system's C: drive and execute arbitrary code. **Key Points:** - A Server-Side Request Forgery (SSRF) vulnerability in Docker Desktop for Windows (CVE-2025-9074) allowed a full container escape. - The vulnerability existed in unpatched versions of Docker Desktop, specifically those attributed to the "4.44.3" patch. - An attacker could exploit this by sending an unauthenticated API request from a container to a specific IP address and port. - This exploit allowed mounting the host's C: drive into the container, granting full access to the Windows host. - The vulnerability was discovered by Philippe Dugre and was replicated on macOS. - Docker has since fixed the vulnerability in version 4.44.3. - The exploit requires the container to have network access to the Docker API endpoint. ![Screenshot at 00:03: The video displays a blog post detailing the "Full Docker Escape on Windows Docker Desktop" vulnerability \(CVE-2025-2074\), highlighting the severity and the need for an update.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-00-03.png) **Context:** The video discusses a critical vulnerability found in Docker Desktop for Windows, identified as CVE-2025-9074. This vulnerability, discovered by Philippe Dugre, allowed for a full container escape, meaning an attacker could break out of the containerized environment and gain access to the underlying host system. The exploit leveraged an unauthenticated API endpoint, which was a significant oversight in the software's security design. ## Detailed Analysis The video explains a critical container escape vulnerability (CVE-2025-9074) in Docker Desktop for Windows. This flaw allowed unauthenticated API requests from a container to access the host's C: drive, enabling attackers to execute arbitrary code and gain full control over the Windows host system. The vulnerability was discovered accidentally by security researcher Philippe Dugre, who found that unpatched versions of Docker Desktop could be exploited by simply making a request to the Docker API. This was possible because the container was not properly isolated from the host's file system and API endpoints. The exploit involves creating a container, mounting the host's C: drive, and then executing commands within that container to write or read files on the host. The vulnerability was confirmed to be present on both Windows and macOS versions of Docker Desktop. The presenter emphasizes that this is a critical issue, as it bypasses the intended isolation mechanisms of containers, allowing for potential system compromise. The fix for this vulnerability was released in version 4.44.3 of Docker Desktop. ### Vulnerability Explained - CVE-2025-9074 allows full container escape on Windows Docker Desktop via unauthenticated API requests. ### Exploitation Method - Attackers can mount the host's C: drive into a container and execute arbitrary code. ### Discovery - Found by Philippe Dugre through accidental discovery and network scanning. ### Impact - Enables attackers to gain full access to the Windows host system. ### Affected Versions - Unpatched versions of Docker Desktop, specifically related to patch "4.44.3". ### Mitigation - Update Docker Desktop to version 4.44.3 or later. ### Key Takeaway - Emphasizes the importance of authenticating all control-plane endpoints and enforcing network segmentation. ![Screenshot at 00:03: The blog post title "SSRF is enough: Full Docker Escape on Windows Docker Desktop" clearly indicates the vulnerability being discussed.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-00-03.png) ![Screenshot at 00:11: The video transitions to a demonstration of the exploit using a command-line interface, showing the process of creating and interacting with a container.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-00-11.png) ![Screenshot at 00:24: A visual representation of a container and its relationship to the operating system is shown, illustrating the isolation concept.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-00-24.png) ![Screenshot at 00:44: A diagram shows how containers typically interact with the operating system, highlighting the intended isolation.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-00-44.png) ![Screenshot at 01:11: The presenter explains the concept of containers and their isolation from the host operating system.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-01-11.png) ![Screenshot at 01:44: A diagram illustrates the isolation between containers and the operating system, showing how containers are sandboxed.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-01-44.png) ![Screenshot at 02:03: The specific CVE number \(CVE-2025-9074\) for the vulnerability is highlighted.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-02-03.png) ![Screenshot at 02:18: The Docker Desktop interface is shown, specifically the 'Containers' and 'Images' sections, providing context for the demonstration.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-02-18.png) ![Screenshot at 02:54: A comparison table shows the significant difference in CVE count and size between ChainGuard's images and an alternative, demonstrating ChainGuard's security posture.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-02-54.png) ![Screenshot at 03:42: The PoC code is displayed, showing the specific commands used to exploit the vulnerability, including mounting the host's C: drive into the container.](https://ss.rapidrecap.app/screens/QgVR1dxy6zk/00-03-42.png)