Description
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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-2367 | 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. |
Github GHSA |
GHSA-mc8v-mgrf-8f4m | Clarify Content-Type handling |
References
History
Wed, 16 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Sun, 08 Sep 2024 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat acm
|
|
| CPEs | cpe:/a:redhat:acm:2.4::el8 cpe:/a:redhat:acm:2.5::el8 |
|
| Vendors & Products |
Redhat acm
|
Mon, 19 Aug 2024 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:acm:2.5::el8 |
|
| Vendors & Products |
Redhat acm
|
Subscriptions
Fedoraproject
Subscribe
Fedora
Subscribe
Linuxfoundation
Subscribe
Open Container Initiative Distribution Specification
Subscribe
Open Container Initiative Image Format Specification
Subscribe
Redhat
Subscribe
Acm
Subscribe
Advanced Cluster Security
Subscribe
Container Native Virtualization
Subscribe
Enterprise Linux
Subscribe
Openshift
Subscribe
Openshift Api Data Protection
Subscribe
Rhmt
Subscribe
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2024-08-04T03:08:31.262Z
Reserved: 2021-09-15T00:00:00.000Z
Link: CVE-2021-41190
No data.
Status : Modified
Published: 2021-11-17T20:15:10.333
Modified: 2024-11-21T06:25:43.537
Link: CVE-2021-41190
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA