First published: Thu Feb 01 2024(Updated: )
Moby could provide weaker than expected security, caused by improper cache validation in the classic builder cache system. By persuading a victim to open a specially crafted file, a remote attacker could exploit this vulnerability to conduct a cache poisoning attack.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/moby/moby | >=25.0.0<25.0.2 | 25.0.2 |
go/github.com/moby/moby | <24.0.9 | 24.0.9 |
go/github.com/docker/docker | <24.0.9 | 24.0.9 |
go/github.com/docker/docker | >=25.0.0<25.0.2 | 25.0.2 |
Moby | <24.0.9 | |
Moby | >=25.0.0<25.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-24557 is classified based on its potential impact on system integrity and security.
To mitigate CVE-2024-24557, upgrade to Moby version 25.0.2 or 24.0.9 as soon as possible.
CVE-2024-24557 affects Moby versions prior to 25.0.2 and Docker versions prior to 24.0.9.
CVE-2024-24557 involves cache poisoning and issues with certain Dockerfile instructions like HEALTHCHECK and ONBUILD.
Yes, CVE-2024-24557 specifically impacts the Moby and Docker software containerization projects.