Data corruption or crashes via unsynchronized writes
Published Nov 29, 2024 · Updated May 1, 2025
Race condition in Moby 25.0.3 and earlier allows remote authenticated users to corrupt progress output or crash applications. The progressOutput.WriteProgress method writes formatted records to a shared io.Writer without synchronization, allowing concurrent records to interleave. Low-privileged network access must expose a code path that triggers concurrent progress writes; effects are limited to corrupt output or an application crash.
Summary
What happened
Race condition in Moby 25.0.3 and earlier allows remote authenticated users to corrupt progress output or crash applications. The progressOutput.WriteProgress method writes formatted records to a shared io.Writer without synchronization, allowing concurrent records to interleave. Low-privileged network access must expose a code path that triggers concurrent progress writes; effects are limited to corrupt output or an application crash.
The record
- CVE
- CVE-2024-36623
- Published
- Nov 29, 2024
- Updated
- May 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 29, 2024CVE publishedPublication date reported by the CVE source.
- May 1, 2025Record 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.
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