Build cache poisoning via incomplete instruction matching
Published Feb 1, 2024 · Updated May 15, 2025
Cache poisoning in the Moby classic builder before 24.0.9 and 25.0.0 through 25.0.1 allows attackers to substitute cached build steps. The cache lookup treats images built from different Dockerfiles as valid candidates because changes to instructions such as HEALTHCHECK and ONBUILD do not invalidate the key. On 23.0 and later, exploitation requires classic-builder use through DOCKER_BUILDKIT=0, the /build API, or the ImageBuild client default, enabling malicious image content to alter resulting builds.
Summary
What happened
Cache poisoning in the Moby classic builder before 24.0.9 and 25.0.0 through 25.0.1 allows attackers to substitute cached build steps. The cache lookup treats images built from different Dockerfiles as valid candidates because changes to instructions such as HEALTHCHECK and ONBUILD do not invalidate the key. On 23.0 and later, exploitation requires classic-builder use through DOCKER_BUILDKIT=0, the /build API, or the ImageBuild client default, enabling malicious image content to alter resulting builds.
The record
- CVE
- CVE-2024-24557
- Published
- Feb 1, 2024
- Updated
- May 15, 2025
- Vendor
- Moby Project
- Product
- Moby
- Classifications
- T1195.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 1, 2024CVE publishedPublication date reported by the CVE source.
- May 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 24.0.9
- Affected versionversion=>= 25.0.0, < 25.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo