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 will be 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.
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/distribution-spec/
* Email us at [email protected]
| Score | Percentile |
|---|---|
| 0.40% | 60.51% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 3.0 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-mc8v-mgrf-8f4m ↗ |
| CVE | CVE-2021-41190 ↗ |
| CWE id | Name |
|---|---|
| CWE-843 | Access of Resource Using Incompatible Type ('Type Confusion') |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| go | github.com/opencontainers/distribution-spec | < 1.0.1 | 1.0.1 | — |