Skip to content

Ambiguous OCI manifest parsing

Low severity GitHub Reviewed Published Nov 18, 2021 in containerd/containerd • Updated Mar 30, 2023

Package

gomod github.com/containerd/containerd (Go)

Affected versions

< 1.4.12
>= 1.5.0, < 1.5.8

Patched versions

1.4.12
1.5.8

Description

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

GHSA-mc8v-mgrf-8f4m
GHSA-77vh-xpmg-72qh

For more information

If you have any questions or comments about this advisory:

References

@dmcgowan dmcgowan published to containerd/containerd Nov 18, 2021
Reviewed Nov 18, 2021
Published to the GitHub Advisory Database Nov 18, 2021
Last updated Mar 30, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-5j5w-g665-5m35

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.