4
CVSSv2

CVE-2021-41190

Published: 17/11/2021 Updated: 22/11/2021
CVSS v2 Base Score: 4 | Impact Score: 2.9 | Exploitability Score: 8
CVSS v3 Base Score: 5 | Impact Score: 1.4 | Exploitability Score: 3.1
Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

Vulnerability Summary

The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently. The OCI Distribution Specification has been updated to require that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.

Most Upvoted Vulmon Research Post

There is no Researcher post for this vulnerability
Would you like to share something about it? Sign up now to share your knowledge with the community.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

linuxfoundation open container initiative distribution specification

linuxfoundation open container initiative image format specification

Vendor Advisories

The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content In the OCI Distribution Specification version 100 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations Documents that contain both “manifests” and ...
In the OCI Distribution Specification version 100 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header If a ...

Mailing Lists

Severity: MEDIUM (moderate in Github GHSA) Description: The specifications themselves needed additional clarification so that implementations of container registries, and the clients that parse data received from registries can have more securely defined behavior The undefined behavior this advisory addresses is a "type confusion" where a JSON ...