CVE-2024-24557 [Medium] | Security Vulnerability in Moby

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2024-02-10	0.04%	0.05%	+0.01%
2	2024-02-08	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2024-02-10

0.04%

0.05%

+0.01%

2024-02-08

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.9	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.0	5.3	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.9

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.0

5.3

[email protected]

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2024-24557

vendor	priority	summary	link
`alpine`	—	CVE-2024-24557: 1 source package rows (docker); 5 state rows across 5 repos (3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 5, open 0.	https://security.alpinelinux.org/vuln/CVE-2024-24557
`debian`	not yet assigned	CVE-2024-24557 not yet assigned priority: Debian including 1 source packages (docker.io), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2.	https://security-tracker.debian.org/tracker/CVE-2024-24557
`gentoo`	low	CVE-2024-24557: 1 GLSA(s) (202409-29), 1 atom(s) (app-containers/docker); latest impact low.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-24557
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2024-24557
`suse`	medium	CVE-2024-24557 severity moderate: SUSE including 13 source package names (docker, docker-bash-completion, …), 101 product×package rows across 38 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE CaaS Platform 4.0, … (38 product lines)): Known Not Affected 97, Fixed 4.	https://www.suse.com/security/cve/CVE-2024-24557/
`ubuntu`	medium	CVE-2024-24557 medium priority: Ubuntu including 2 source packages (docker.io, docker.io-app), 22 status rows across 11 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, needed 5, not-affected 3, released 3, DNE 2, needs-triage 2.	https://ubuntu.com/security/CVE-2024-24557

Affected software / configurations for CVE-2024-24557

Vendor	Product	Version	Raw CPE
mobyproject	moby	< 24.0.9	cpe:2.3:a:mobyproject:moby::::::::
mobyproject	moby	>= 25.0.0, < 25.0.2	cpe:2.3:a:mobyproject:moby::::::::

References for CVE-2024-24557

URL	Tags
https://github.com/moby/moby/commit/3e230cfdcc989dc524882f6579f9e0dac77400ae	Patch
https://github.com/moby/moby/security/advisories/GHSA-xw73-rw38-6vjc	Vendor Advisory

URL

CVE-2024-24557 | Moby classic builder cache poisoning

Exploit prediction scoring system (EPSS) score for CVE-2024-24557

Common vulnerability scoring system (CVSS) metrics for CVE-2024-24557

Weakness enumeration for CVE-2024-24557

GitHub Security Advisory for CVE-2024-24557

OS Trackers for CVE-2024-24557

Affected software / configurations for CVE-2024-24557

References for CVE-2024-24557