Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2024-24557: Moby classic builder cache poisoning

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: docker (Alpine:v3.18) 25.0.2-r0; docker.io (Debian:13) 26.1.4+dfsg1-9; github.com/docker/docker (Go) 25.0.2, 25.0.2+incompatible, 24.0.9+incompatible.

Low priority for now. Upgrade to docker (Alpine:v3.18) 25.0.2-r0; docker.io (Debian:13) 26.1.4+dfsg1-9; github.com/docker/docker (Go) 25.0.2, 25.0.2+incompatible, 24.0.9+incompatible or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Feb 1, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 17th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · GitHub_M
6.9
0.9 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-24557

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for mobyproject records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
mobyprojectmoby

Using moby? Add it to your stack and be the first to know about CVEs like this one. (Docker)

Watch new CVEs for moby

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • mobyproject mobybefore 24.0.9
  • mobyproject moby25.0.0 and later · before 25.0.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • moby moby

    • >= 25.0.0, < 25.0.2, < 24.0.9affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.18dockerbefore 25.0.2-r025.0.2-r0
Debian:12docker.iofrom 0—
Debian:13docker.iobefore 26.1.4+dfsg1-926.1.4+dfsg1-9
Gogithub.com/docker/dockerfrom 25.0.0 · before 25.0.225.0.2
Gogithub.com/docker/dockerfrom 25.0.0+incompatible · before 25.0.2+incompatible25.0.2+incompatible
Gogithub.com/docker/dockerbefore 24.0.9+incompatible24.0.9+incompatible
Gogithub.com/docker/dockerbefore 24.0.924.0.9
Gogithub.com/moby/mobyfrom 25.0.0 · before 25.0.225.0.2
Gogithub.com/moby/mobyfrom 25.0.0+incompatible · before 25.0.2+incompatible25.0.2+incompatible
Gogithub.com/moby/mobybefore 24.0.9+incompatible24.0.9+incompatible
Gogithub.com/moby/mobybefore 24.0.924.0.9
openSUSE:Tumbleweedforgejo-runnerbefore 3.5.1-1.13.5.1-1.1

Same product

mobyproject: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-28840moby/moby's dockerd daemon encrypted overlay network may be unauthenticated
    35Monitor
  • CVE-2024-36623moby through v25.0.3 has a Race Condition vulnerability in the streamformatter package which can be used to trigger multiple concurrent writ
    32Monitor
  • CVE-2024-29018External DNS requests from 'internal' networks could lead to data exfiltration
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-28841Apr 4, 2023 · moby/moby's dockerd daemon encrypted overlay network traffic may be unencrypted
    27Monitor
  • ← EarlierCVE-2023-28842Apr 4, 2023 · moby/moby's dockerd daemon encrypted overlay network with a single endpoint is unauthenticated
    27Monitor
  • Later →CVE-2024-32473Apr 18, 2024 · Moby IPv6 enabled on IPv4-only network interfaces
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:docker25.0.2-r0 · Alpine:v3.18Package registry (OSV)
debian:docker.io26.1.4+dfsg1-9 · Debian:13Package registry (OSV)
Go:github.com/docker/docker24.0.9Package registry (OSV)
Go:github.com/docker/docker24.0.9+incompatiblePackage registry (OSV)
Go:github.com/docker/docker25.0.2Package registry (OSV)
Go:github.com/docker/docker25.0.2+incompatiblePackage registry (OSV)
Go:github.com/moby/moby24.0.9Package registry (OSV)
Go:github.com/moby/moby24.0.9+incompatiblePackage registry (OSV)
Go:github.com/moby/moby25.0.2Package registry (OSV)
Go:github.com/moby/moby25.0.2+incompatiblePackage registry (OSV)
opensuse:forgejo-runner3.5.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-345 · Insufficient Verification of Data Authenticity

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records