CVE-2021-21285 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in github.com/moby/moby. A fix is available for github.com/moby/moby — see the affected versions and patch details below.
moby docker daemon crash during image pull of malicious image
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/moby/moby🐹github.com/moby/mobyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Pulling an intentionally malformed Docker image manifest crashes the dockerd daemon.
Patches
Versions 20.10.3 and 19.03.15 contain patches that prevent the daemon from crashing.
Credits
Maintainers would like to thank Josh Larsen, Ian Coldwater, Duffie Cooley, Rory McCune for working on the vulnerability and Brad Geesaman for responsibly disclosing it to [email protected].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/moby/moby | all versions | 19.3.15go get github.com/moby/moby@v19.3.15 |
| 🐹Go | github.com/moby/moby | ≥ 20.10.0-beta1&&< 20.10.3 | 20.10.3go get github.com/moby/moby@v20.10.3 |
Affected Products
debian linuxdebiandockerdockere-series santricity os controllernetappDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/moby/moby, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/moby/moby to 19.3.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21285 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2021-21285 in your dependencies?
Find it across Go, including transitive dependencies.