Resource exhaustion via unlocked layer registration
Published Nov 29, 2024 · Updated Dec 4, 2024
Race condition in Moby 25.0.5 allows remote authenticated users to exhaust resources by submitting concurrent image builds. EnsureLayer updates the shared refs map without a per-layer lock, so concurrent exporters can register the same layer twice and corrupt its reference count. Access to the build interface and overlapping builds are required; leaked layers consume resources until the service is interrupted.
Summary
What happened
Race condition in Moby 25.0.5 allows remote authenticated users to exhaust resources by submitting concurrent image builds. EnsureLayer updates the shared refs map without a per-layer lock, so concurrent exporters can register the same layer twice and corrupt its reference count. Access to the build interface and overlapping builds are required; leaked layers consume resources until the service is interrupted.
The record
- CVE
- CVE-2024-36621
- Published
- Nov 29, 2024
- Updated
- Dec 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 29, 2024CVE publishedPublication date reported by the CVE source.
- Dec 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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