# CVE-2021-41190: Clarify Content-Type handling in OCI spec - **Severity:** Low 3.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 17 Nov 2021 - **Updated:** 4 Aug 2024 - **Also known as:** AZL-44865, AZL-44925, CLEANSTART-2025-HQ55158, CLEANSTART-2026-NW72485, GHSA-mc8v-mgrf-8f4m, GHSA-xmmx-7jpf-fx42, GO-2024-2914, MGASA-2021-0531, SUSE-SU-2025:02282-1, UBUNTU-CVE-2021-41190, openSUSE-SU-2021:1525-1, openSUSE-SU-2024:11646-1, openSUSE-SU-2024:11647-1, openSUSE-SU-2024:11659-1, openSUSE-SU-2025:15166-1 ## What is CVE-2021-41190? CVE-2021-41190 is a low-severity vulnerability in Fedoraproject Fedora, published on 17 Nov 2021. ### Official 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. Weakness: CWE-843 (Access of Resource Using Incompatible Type) ## Which versions are affected by CVE-2021-41190? 8 open source packages ship an affected version, including github.com/docker/docker, github.com/moby/moby and github.com/opencontainers/distribution-spec. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/docker/docker` | Go | All versions | 20.10.11 | | `github.com/docker/docker` | Go | All versions | 20.10.11 | | `github.com/docker/docker` | Go | All versions | 20.10.11+incompatible | | `github.com/moby/moby` | Go | All versions | 20.10.11 | | `github.com/moby/moby` | Go | All versions | 20.10.11 | | `github.com/moby/moby` | Go | All versions | 20.10.11+incompatible | | `github.com/opencontainers/distribution-spec` | Go | All versions | 1.0.1 | | `github.com/opencontainers/distribution-spec` | Go | All versions | 1.0.1 | | `umoci` | SUSE:Enterprise Storage 7.1 | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Manager Proxy 4.3 | All versions | 0.5.0-150000.3.15.1 | | `umoci` | SUSE:Manager Server 4.3 | All versions | 0.5.0-150000.3.15.1 | | `singularity` | SUSE:Package Hub 15 SP3 | All versions | 3.8.5-bp153.2.10.1 | | `singularity` | openSUSE:Leap 15.3 | All versions | 3.8.5-bp153.2.10.1 | | `umoci` | openSUSE:Leap 15.6 | All versions | 0.5.0-150000.3.15.1 | | `containerd` | openSUSE:Tumbleweed | All versions | 1.4.12-1.1 | | `docker` | openSUSE:Tumbleweed | All versions | 20.10.11_ce-1.1 | | `singularity` | openSUSE:Tumbleweed | All versions | 3.8.5-1.1 | | `umoci` | openSUSE:Tumbleweed | All versions | 0.5.0-1.1 | Products: Fedoraproject Fedora, Linuxfoundation Open Container Initiative Distribution Specification, Linuxfoundation Open Container Initiative Image Format Specification. ## How do I fix CVE-2021-41190? Upgrade github.com/docker/docker to a fixed version for your release line: 20.10.11 or 20.10.11+incompatible. ## Is CVE-2021-41190 being exploited? There is no known exploitation of CVE-2021-41190 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-41190 and fix it if it is affected. What it is: CVE-2021-41190 is a low-severity vulnerability in Fedoraproject Fedora, published on 17 Nov 2021. Exploitation: There is no known exploitation of CVE-2021-41190 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/docker/docker (Go): affected all versions; fixed in 20.10.11 - github.com/docker/docker (Go): affected all versions; fixed in 20.10.11 - github.com/docker/docker (Go): affected all versions; fixed in 20.10.11+incompatible - github.com/moby/moby (Go): affected all versions; fixed in 20.10.11 - github.com/moby/moby (Go): affected all versions; fixed in 20.10.11 - github.com/moby/moby (Go): affected all versions; fixed in 20.10.11+incompatible - github.com/opencontainers/distribution-spec (Go): affected all versions; fixed in 1.0.1 - github.com/opencontainers/distribution-spec (Go): affected all versions; fixed in 1.0.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2021-41190/ (Markdown: https://insights.sbomify.com/CVE-2021-41190/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-41190 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-41190 - OSV: https://osv.dev/vulnerability/CVE-2021-41190 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-41190/ Summaries are generated and may contain mistakes; the official description above is the record.