Daemon crash via unvalidated manifest layer digest
Published Feb 2, 2021 · Updated Aug 3, 2024
Denial of service in Moby before 19.03.15 and 20.0.0 through 20.10.2 allows remote attackers to crash dockerd via a malformed image manifest. The schema 1, schema 2, and BuildKit pull paths accept layer digests without calling Digest.Validate, allowing an invalid digest to reach code that terminates the daemon. A user with daemon access must initiate the image pull; the crash interrupts workloads managed by that daemon.
Summary
What happened
Denial of service in Moby before 19.03.15 and 20.0.0 through 20.10.2 allows remote attackers to crash dockerd via a malformed image manifest. The schema 1, schema 2, and BuildKit pull paths accept layer digests without calling Digest.Validate, allowing an invalid digest to reach code that terminates the daemon. A user with daemon access must initiate the image pull; the crash interrupts workloads managed by that daemon.
The record
- CVE
- CVE-2021-21285
- Published
- Feb 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- Moby Project
- Product
- Moby
- Classifications
- CWE-754, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=< 19.03.15
- Affected versionversion=>= 20.0.0, < 20.10.3
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