Access of Resource Using Incompatible Type ('Type Confusion') Affecting openshift-clients package, versions <0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el7


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.13% (51st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Access of Resource Using Incompatible Type ('Type Confusion') vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-OPENSHIFTCLIENTS-5394976
  • published24 Nov 2021
  • disclosed17 Nov 2021

Introduced: 17 Nov 2021

CVE-2021-41190  (opens in a new tab)
CWE-843  (opens in a new tab)

How to fix?

Upgrade RHEL:7 openshift-clients to version 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el7 or higher.
This issue was patched in RHSA-2022:0055.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openshift-clients package and not the openshift-clients package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

References

CVSS Scores

version 3.1