Moby classic builder cache poisoning

Summary

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.

Timeline

1. Feb 1, 2024, 4:26 PM UTCCVE published
2. May 15, 2025, 3:20 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. May 15, 2025, 3:27 PM UTCRecord last updated

Affected versions

• moby moby

  From 25.0.0 · fixed in 25.0.2; fixed in 24.0.9

• github.com/docker/dockerGo

  fixed in 24.0.9

• github.com/moby/mobyGo

  fixed in 24.0.9

• github.com/moby/mobyGo

  From 25.0.0 · fixed in 25.0.2

• github.com/docker/dockerGo

  From 25.0.0 · fixed in 25.0.2

• github.com/docker/dockerGo

  fixed in 24.0.9+incompatible; From 25.0.0+incompatible · fixed in 25.0.2+incompatible

• github.com/moby/mobyGo

  fixed in 24.0.9+incompatible; From 25.0.0+incompatible · fixed in 25.0.2+incompatible

References 2