An attacker who controls the registry, a mirror, or the network path to it may be able to serve arbitrary image content in response to a pul
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.6.0, 0.52.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The container and containerization tools are affected when they pull images by digest. An attacker who controls the registry, a mirror, or the network path could substitute different image content, so users run an image other than the one they pinned.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
An attacker who controls the registry, a mirror, or the network path to it may be able to serve arbitrary image content in response to a pull by digest, so that a user runs an image other than the one they pinned. The fix compares the returned digest to the pinned digest and fails the pull on a mismatch. Tag pulls are exempt, because a tag is mutable by design. The fix also verifies the hash of manifests and blobs when they are fetched. This vulnerability is addressed in container version 1.6.0 and containerization version 0.52.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Apple container
fixed in 1.6.0
- Apple containerization
fixed in 0.52.1