Skip to content

Clarify Content-Type handling

Low severity GitHub Reviewed Published Nov 17, 2021 in opencontainers/distribution-spec • Updated Feb 1, 2023

Package

gomod github.com/opencontainers/distribution-spec (Go)

Affected versions

< 1.0.1

Patched versions

1.0.1

Description

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

GHSA-77vh-xpmg-72qh

For more information

If you have any questions or comments about this advisory:

References

@vbatts vbatts published to opencontainers/distribution-spec Nov 17, 2021
Published by the National Vulnerability Database Nov 17, 2021
Reviewed Nov 17, 2021
Published to the GitHub Advisory Database Nov 18, 2021
Last updated Feb 1, 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

EPSS score

0.101%
(42nd percentile)

Weaknesses

CVE ID

CVE-2021-41190

GHSA ID

GHSA-mc8v-mgrf-8f4m

Source code

Credits

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