Lucene search

K
osvGoogleOSV:GHSA-MC8V-MGRF-8F4M
HistoryNov 18, 2021 - 4:13 p.m.

Clarify Content-Type handling

2021-11-1816:13:08
Google
osv.dev
23
oci distribution
content-type
mediatype
manifest
index
layers
config
security advisory
registry
push
pull operations

EPSS

0.001

Percentile

48.7%

Impact

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.

Patches

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.

Workarounds

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.

References

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:

References