github.com/containerd/containerd
Affected
- introduced
0, fixed1.4.12(semver)
Fixed versions
1.4.12
Fix
- Fixed version
1.4.12go get github.com/containerd/[email protected]
Advisory
Also known as: GO-2022-0360
Ambiguous OCI manifest parsing
Impact
In the OCI Distribution Specification version 1.0.0 and prior and in the OCI Image Specification version 1.0.1 and prior, manifest and index documents are ambiguous without an accompanying Content-Type HTTP header. Versions of containerd prior to 1.4.12 and 1.5.8 treat the Content-Type header as trusted and deserialize the document according to that header. If the Content-Type header changed between pulls of the same ambiguous document (with the same digest), the document may be interpreted differently, meaning that the digest alone is insufficient to unambiguously identify the content of the image.
Patches
This issue has been fixed in containerd 1.4.12 and 1.5.8. Image pulls for manifests that contain a “manifests” field or indices which contain a “layers” field are rejected.
Workarounds
Ensure you only pull images from trusted sources.
References
https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
For more information
If you have any questions or comments about this advisory:
Low Basis: The source's own band: LOW
0, fixed 1.4.12 (semver)1.4.12
1.4.12go get github.com/containerd/[email protected]1.5.0, fixed 1.5.8 (semver)1.5.8
1.5.8go get github.com/containerd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0