| Name | CVE-2024-24557 |
| Description | Moby is an open-source project created by Docker to enable software containerization. The classic builder cache system is prone to cache poisoning if the image is built FROM scratch. Also, changes to some instructions (most important being HEALTHCHECK and ONBUILD) would not cause a cache miss. An attacker with the knowledge of the Dockerfile someone is using could poison their cache by making them pull a specially crafted image that would be considered as a valid cache candidate for some build steps. 23.0+ users are only affected if they explicitly opted out of Buildkit (DOCKER_BUILDKIT=0 environment variable) or are using the /build API endpoint. All users on versions older than 23.0 could be impacted. Image build API endpoint (/build) and ImageBuild function from github.com/docker/docker/client is also affected as it the uses classic builder by default. Patches are included in 24.0.9 and 25.0.2 releases. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| docker.io (PTS) | buster, buster (security) | 18.09.1+dfsg1-7.1+deb10u3 | vulnerable |
| bullseye | 20.10.5+dfsg1-1+deb11u2 | vulnerable |
| bookworm | 20.10.24+dfsg1-1 | vulnerable |
| trixie, sid | 20.10.25+dfsg1-2 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| docker.io | source | (unstable) | (unfixed) | | | |
Notes
[bookworm] - docker.io <no-dsa> (Minor issue)
[bullseye] - docker.io <no-dsa> (Minor issue)
[buster] - docker.io <no-dsa> (Minor issue with workarounds)
https://github.com/moby/moby/commit/3e230cfdcc989dc524882f6579f9e0dac77400ae
https://github.com/moby/moby/security/advisories/GHSA-xw73-rw38-6vjc
Workarounds exists (cf. GHSA-xw73-rw38-6vjc): Avoid using the cache or use Buildkit