ghsa-xw73-rw38-6vjc
Vulnerability from github
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.
For example, an attacker could create an image that is considered as a valid cache candidate for:
FROM scratch
MAINTAINER Pawel
when in fact the malicious image used as a cache would be an image built from a different Dockerfile.
In the second case, the attacker could for example substitute a different HEALTCHECK command.
Impact
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 (which uses the classic builder by default).
All users on versions older than 23.0 could be impacted. An example could be a CI with a shared cache, or just a regular Docker user pulling a malicious image due to misspelling/typosquatting.
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
Patches are included in Moby releases:
- v25.0.2
- v24.0.9
- v23.0.10
Workarounds
- Use
--no-cacheor use Buildkit if possible (DOCKER_BUILDKIT=1, it's default on 23.0+ assuming that the buildx plugin is installed). - Use
Version = types.BuilderBuildKitorNoCache = trueinImageBuildOptionsforImageBuildcall.
{ affected: [ { package: { ecosystem: "Go", name: "github.com/docker/docker", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "24.0.9", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Go", name: "github.com/moby/moby", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "24.0.9", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Go", name: "github.com/moby/moby", }, ranges: [ { events: [ { introduced: "25.0.0", }, { fixed: "25.0.2", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Go", name: "github.com/docker/docker", }, ranges: [ { events: [ { introduced: "25.0.0", }, { fixed: "25.0.2", }, ], type: "ECOSYSTEM", }, ], }, ], aliases: [ "CVE-2024-24557", ], database_specific: { cwe_ids: [ "CWE-345", "CWE-346", ], github_reviewed: true, github_reviewed_at: "2024-02-01T20:51:19Z", nvd_published_at: "2024-02-01T17:15:10Z", severity: "MODERATE", }, details: "The classic builder cache system is prone to cache poisoning if the image is built `FROM scratch`.\nAlso, changes to some instructions (most important being `HEALTHCHECK` and `ONBUILD`) would not cause a cache miss.\n\n\nAn 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.\n\nFor example, an attacker could create an image that is considered as a valid cache candidate for:\n```\nFROM scratch\nMAINTAINER Pawel\n```\n\nwhen in fact the malicious image used as a cache would be an image built from a different Dockerfile.\n\nIn the second case, the attacker could for example substitute a different `HEALTCHECK` command.\n\n\n### Impact\n\n23.0+ users are only affected if they explicitly opted out of Buildkit (`DOCKER_BUILDKIT=0` environment variable) or are using the `/build` API endpoint (which uses the classic builder by default).\n\nAll users on versions older than 23.0 could be impacted. An example could be a CI with a shared cache, or just a regular Docker user pulling a malicious image due to misspelling/typosquatting.\n\nImage build API endpoint (`/build`) and `ImageBuild` function from `github.com/docker/docker/client` is also affected as it the uses classic builder by default. \n\n\n### Patches\n\nPatches are included in Moby releases:\n\n- v25.0.2\n- v24.0.9\n- v23.0.10\n\n### Workarounds\n\n- Use `--no-cache` or use Buildkit if possible (`DOCKER_BUILDKIT=1`, it's default on 23.0+ assuming that the buildx plugin is installed).\n- Use `Version = types.BuilderBuildKit` or `NoCache = true` in `ImageBuildOptions` for `ImageBuild` call.\n\n", id: "GHSA-xw73-rw38-6vjc", modified: "2024-07-05T18:59:04Z", published: "2024-02-01T20:51:19Z", references: [ { type: "WEB", url: "https://github.com/moby/moby/security/advisories/GHSA-xw73-rw38-6vjc", }, { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2024-24557", }, { type: "WEB", url: "https://github.com/moby/moby/commit/3e230cfdcc989dc524882f6579f9e0dac77400ae", }, { type: "WEB", url: "https://github.com/moby/moby/commit/fca702de7f71362c8d103073c7e4a1d0a467fadd", }, { type: "WEB", url: "https://github.com/moby/moby/commit/fce6e0ca9bc000888de3daa157af14fa41fcd0ff", }, { type: "PACKAGE", url: "https://github.com/moby/moby", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L", type: "CVSS_V3", }, ], summary: "Classic builder cache poisoning", }
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.