CVE-2024-24557
Moby classic builder cache poisoning
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.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
Exploit likelihood
What each source reports
CVE List Score used
6.9
Moby classic builder cache poisoning
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.
- Record
CVE-2024-24557- CVSS 3.1
- 6.9 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L - Weakness
- CWE-346, CWE-345
- Updated
- 2026-11-02
EUVDEUVD-2024-0773
6.9
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.
- Record
EUVD-2024-0773- CVSS 3.1
- 6.9 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-xw73-rw38-6vjc
6.9
Classic builder cache poisoning
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.
- Record
GHSA-xw73-rw38-6vjc- CVSS 3.1
- 6.9 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L - Weakness
- CWE-345, CWE-346
- Updated
- 2026-11-02
NVD
6.9
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.
- Record
CVE-2024-24557- CVSS 3.1
- 6.9 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L - CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-345, CWE-346
- Updated
- 2026-11-02
OSVALPINE-CVE-2024-24557
7.8
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.
- Record
ALPINE-CVE-2024-24557- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-03
OSVAZL-34275
7.8
CVE-2024-24557 affecting package moby-engine for versions less than 20.10.27-3
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.
- Record
AZL-34275- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Show 9 moreShow less
OSVAZL-35002
7.8
CVE-2024-24557 affecting package moby-engine for versions less than 25.0.3-1
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.
- Record
AZL-35002- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVBELL-CVE-2024-24557
7.8
- Record
BELL-CVE-2024-24557- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSV
6.9
Moby classic builder cache poisoning
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.
- Record
CVE-2024-24557- CVSS 3.1
- 6.9 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L - Weakness
- CWE-345, CWE-346
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2024-24557
7.8
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.
- Record
DEBIAN-CVE-2024-24557- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-xw73-rw38-6vjc
6.9
Classic builder cache poisoning
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.
- Record
GHSA-xw73-rw38-6vjc- CVSS 3.1
- 6.9 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L - Weakness
- CWE-345, CWE-346
- Updated
- 2026-11-02
OSVOESA-2024-1302
6.9
docker security update
Docker is an open source project to build, ship and run any application as a lightweight container.
Security Fix(es):
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.(CVE-2024-24557)
- Record
OESA-2024-1302- CVSS 3.1
- 6.9 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L - Updated
- 2026-11-02
OSVUBUNTU-CVE-2024-24557
6.9
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.
- Record
UBUNTU-CVE-2024-24557- CVSS 3.1
- 6.9 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L - CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGO-2024-2512 No score
Classic builder cache poisoning in github.com/docker/docker
Classic builder cache poisoning in github.com/docker/docker
- Record
GO-2024-2512- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:14287-1 No score
forgejo-runner-3.5.1-1.1 on GA media
These are all security issues fixed in the forgejo-runner-3.5.1-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:14287-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/docker/dockerGo |
25.0.0 up to 25.0.2 | 25.0.2 |
github.com/docker/dockerGo |
before 24.0.9 | 24.0.9 |
github.com/moby/mobyGo |
before 24.0.9 | 24.0.9 |
github.com/moby/mobyGo |
25.0.0 up to 25.0.2 | 25.0.2 |
dockerAlpine:v3.18 |
before 25.0.2-r0 | 25.0.2-r0 |
dockerAlpine:v3.19 |
before 25.0.2-r0 | 25.0.2-r0 |
dockerAlpine:v3.20 |
before 25.0.2-r0 | 25.0.2-r0 |
dockerAlpine:v3.21 |
before 25.0.2-r0 | 25.0.2-r0 |
dockerAlpine:v3.22 |
before 25.0.2-r0 | 25.0.2-r0 |
dockerAlpine:v3.23 |
before 25.0.2-r0 | 25.0.2-r0 |
Show 27 moreShow less
| Package | Affected | Fixed |
|---|---|---|
dockerAlpine:v3.24 |
before 25.0.2-r0 | 25.0.2-r0 |
moby-engineAzure Linux:2 |
before 20.10.27-3 | 20.10.27-3 |
moby-engineAzure Linux:3 |
before 25.0.3-1 | 25.0.3-1 |
dockerAlpaquita:23 |
20.10.21-r1 and later | None known |
dockerAlpaquita:stream |
24.0.2-r0 up to 25.0.2-r0 | 25.0.2-r0 |
docker.ioDebian:12 |
All versions, plus listed versions 20.10.24+dfsg1-120.10.24+dfsg1-1+deb12u120.10.25+dfsg1-120.10.25+dfsg1-220.10.25+dfsg1-3 Show 42 moreShow less20.10.25+dfsg1-426.1.4+dfsg1-126.1.4+dfsg1-226.1.4+dfsg1-326.1.4+dfsg1-426.1.4+dfsg1-526.1.4+dfsg1-626.1.4+dfsg1-726.1.4+dfsg1-826.1.4+dfsg1-926.1.4+dfsg2-126.1.4+dfsg3-126.1.5+dfsg1-126.1.5+dfsg1-1026.1.5+dfsg1-226.1.5+dfsg1-326.1.5+dfsg1-426.1.5+dfsg1-526.1.5+dfsg1-626.1.5+dfsg1-726.1.5+dfsg1-826.1.5+dfsg1-927.5.1+dfsg1-127.5.1+dfsg1-227.5.1+dfsg2-127.5.1+dfsg3-127.5.1+dfsg3-227.5.1+dfsg3-327.5.1+dfsg3-427.5.1+dfsg3-527.5.1+dfsg3-627.5.1+dfsg4-127.5.1+dfsg4-228.5.2+dfsg1-128.5.2+dfsg2-128.5.2+dfsg3-128.5.2+dfsg3-228.5.2+dfsg4-128.5.2+dfsg4-228.5.2+dfsg4-328.5.2+dfsg4-428.5.2+dfsg4-5 |
None known |
docker.ioDebian:13 |
before 26.1.4+dfsg1-9 | 26.1.4+dfsg1-9 |
docker.ioDebian:14 |
before 26.1.4+dfsg1-9 | 26.1.4+dfsg1-9 |
github.com/docker/dockerGo |
before 24.0.9+incompatible, 25.0.0+incompatible up to 25.0.2+incompatible | 24.0.9+incompatible25.0.2+incompatible |
github.com/moby/mobyGo |
before 24.0.9+incompatible, 25.0.0+incompatible up to 25.0.2+incompatible | 24.0.9+incompatible25.0.2+incompatible |
dockeropenEuler:20.03-LTS-SP1 |
before engine-18.09.0-263.oe1 | engine-18.09.0-263.oe1 |
dockeropenEuler:20.03-LTS-SP4 |
before engine-18.09.0-263.oe2003sp4 | engine-18.09.0-263.oe2003sp4 |
dockeropenEuler:22.03-LTS |
before engine-18.09.0-334.oe2203sp3 | engine-18.09.0-334.oe2203sp3 |
dockeropenEuler:22.03-LTS-SP1 |
before engine-18.09.0-333.oe2203sp1 | engine-18.09.0-333.oe2203sp1 |
dockeropenEuler:22.03-LTS-SP2 |
before engine-18.09.0-333.oe2203sp2 | engine-18.09.0-333.oe2203sp2 |
dockeropenEuler:22.03-LTS-SP3 |
before engine-18.09.0-334.oe2203sp3 | engine-18.09.0-334.oe2203sp3 |
docker.ioUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 1.13.1-0ubuntu617.03.2-0ubuntu117.03.2-0ubuntu317.03.2-0ubuntu517.12.1-0ubuntu1 Show 22 moreShow less18.06.1-0ubuntu1~18.04.118.06.1-0ubuntu1.2~18.04.118.09.2-0ubuntu1~18.04.118.09.5-0ubuntu1~18.04.218.09.7-0ubuntu1~18.04.118.09.7-0ubuntu1~18.04.318.09.7-0ubuntu1~18.04.419.03.6-0ubuntu1~18.04.119.03.6-0ubuntu1~18.04.219.03.6-0ubuntu1~18.04.320.10.2-0ubuntu1~18.04.220.10.2-0ubuntu1~18.04.320.10.7-0ubuntu1~18.04.120.10.7-0ubuntu1~18.04.220.10.7-0ubuntu5~18.04.220.10.7-0ubuntu5~18.04.320.10.12-0ubuntu2~18.04.120.10.21-0ubuntu1~18.04.220.10.21-0ubuntu1~18.04.320.10.21-0ubuntu1~18.04.3+esm120.10.21-0ubuntu1~18.04.3+esm220.10.21-0ubuntu1~18.04.3+esm3 |
None known |
docker.ioUbuntu:Pro:20.04:LTS |
All versions, plus listed versions 19.03.2-0ubuntu119.03.6-0ubuntu119.03.8-0ubuntu119.03.8-0ubuntu1.20.0419.03.8-0ubuntu1.20.04.1 Show 15 moreShow less19.03.8-0ubuntu1.20.04.220.10.2-0ubuntu1~20.04.220.10.2-0ubuntu1~20.04.320.10.7-0ubuntu1~20.04.120.10.7-0ubuntu1~20.04.220.10.7-0ubuntu5~20.04.120.10.7-0ubuntu5~20.04.220.10.12-0ubuntu2~20.04.120.10.21-0ubuntu1~20.04.120.10.21-0ubuntu1~20.04.220.10.21-0ubuntu1~20.04.420.10.21-0ubuntu1~20.04.520.10.21-0ubuntu1~20.04.620.10.21-0ubuntu1~20.04.6+esm120.10.21-0ubuntu1~20.04.6+esm2 |
None known |
docker.io-appUbuntu:Pro:20.04:LTS |
before 26.1.3-0ubuntu1~20.04.1+esm1, plus listed versions 20.10.25-0ubuntu1~20.04.120.10.25-0ubuntu1~20.04.224.0.5-0ubuntu1~20.04.124.0.7-0ubuntu2~20.04.126.1.3-0ubuntu1~20.04.1 |
26.1.3-0ubuntu1~20.04.1+esm1 |
docker.io-appUbuntu:22.04:LTS |
before 27.5.1-0ubuntu3~22.04.2, plus listed versions 20.10.25-0ubuntu1~22.04.120.10.25-0ubuntu1~22.04.224.0.5-0ubuntu1~22.04.124.0.7-0ubuntu2~22.04.126.1.3-0ubuntu1~22.04.127.5.1-0ubuntu3~22.04.1 |
27.5.1-0ubuntu3~22.04.2 |
docker.ioUbuntu:Pro:22.04:LTS |
All versions, plus listed versions 20.10.7-0ubuntu520.10.7-0ubuntu720.10.12-0ubuntu120.10.12-0ubuntu220.10.12-0ubuntu3 Show 11 moreShow less20.10.12-0ubuntu3+gke1.24.120.10.12-0ubuntu420.10.21-0ubuntu1~22.04.220.10.21-0ubuntu1~22.04.320.10.21-0ubuntu1~22.04.520.10.21-0ubuntu1~22.04.620.10.21-0ubuntu1~22.04.720.10.21-0ubuntu1~22.04.7+esm120.10.21-0ubuntu1~22.04.7+esm220.10.21-0ubuntu1~22.04.820.10.21-0ubuntu1~22.04.8+esm1 |
None known |
docker.io-appUbuntu:24.04:LTS |
before 27.5.1-0ubuntu3~24.04.2, plus listed versions 24.0.5-0ubuntu124.0.7-0ubuntu124.0.7-0ubuntu224.0.7-0ubuntu324.0.7-0ubuntu424.0.7-0ubuntu4.126.1.3-0ubuntu1~24.04.127.5.1-0ubuntu3~24.04.1 |
27.5.1-0ubuntu3~24.04.2 |
docker.ioUbuntu:Pro:24.04:LTS |
All versions, plus listed versions 20.10.24+dfsg1-1ubuntu220.10.25+dfsg1-2ubuntu120.10.25+dfsg1-2ubuntu1+esm120.10.25+dfsg1-2ubuntu1+esm220.10.25+dfsg1-2ubuntu1.24.04.120.10.25+dfsg1-2ubuntu1.24.04.1+esm1 |
None known |
docker.ioUbuntu:25.10 |
All versions, plus listed versions 26.1.5+dfsg1-9ubuntu1 |
None known |
docker.ioUbuntu:26.10 |
All versions, plus listed versions 27.5.1+dfsg4-2ubuntu128.5.2+dfsg4-5ubuntu1 |
None known |
docker.ioUbuntu:26.04:LTS |
All versions, plus listed versions 26.1.5+dfsg1-9ubuntu127.5.1+dfsg4-1ubuntu127.5.1+dfsg4-2ubuntu1 |
None known |
forgejo-runneropenSUSE:Tumbleweed |
before 3.5.1-1.1 | 3.5.1-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, aliases, references | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2024-24557 is a medium vulnerability (CVSS 6.9) in Moby, published February 1, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.26%, the 17th percentile. Fixed in github.com/docker/docker 25.0.2.
References
github.com/moby/moby/security/advisories/GHSA-xw73-rw38-6vjc
github.com/moby/moby/commit/3e230cfdcc989dc524882f6579f9e0dac77400ae
nvd.nist.gov/vuln/detail/CVE-2024-24557
github.com/moby/moby/commit/fca702de7f71362c8d103073c7e4a1d0a467fadd
github.com/moby/moby/commit/fce6e0ca9bc000888de3daa157af14fa41fcd0ff
github.com/advisories/GHSA-xw73-rw38-6vjc
Show 9 moreShow less
security.alpinelinux.org/vuln/CVE-2024-24557
docs.bell-sw.com/security/cves/CVE-2024-24557
github.com/CVEProject/cvelistV5/tree/main/cves/2024/24xxx/CVE-2024-24557.json
security-tracker.debian.org/tracker/CVE-2024-24557
github.com/moby/moby
openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1302
ubuntu.com/security/CVE-2024-24557
cve.org/CVERecord?id=CVE-2024-24557
suse.com/security/cve/CVE-2024-24557