CVE-2021-41190: Clarify Content-Type handling in OCI spec
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 82.8% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: containerd (Alpine:v3.14) 1.5.8-r0; docker (Alpine:v3.14) 20.10.11-r0; podman (Alpine:v3.15) 3.4.4-r0.
- Severity is disputed: the assigning authority (CNA) scores it 3.0, NVD 5.0.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to containerd (Alpine:v3.14) 1.5.8-r0; docker (Alpine:v3.14) 20.10.11-r0; podman (Alpine:v3.15) 3.4.4-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2023-03675
- GHSA-mc8v-mgrf-8f4m
- GO-2024-2914
- openSUSE-SU-2021:1525-1
- openSUSE-SU-2022:0334-1
- openSUSE-SU-2022:23018-1
- openSUSE-SU-2024:11646-1
- openSUSE-SU-2024:11647-1
- openSUSE-SU-2024:11659-1
- openSUSE-SU-2024:11674-1
- openSUSE-SU-2025:15166-1
- RHSA-2022:0055
- RHSA-2022:7457
- RLSA-2022:7457
- SUSE-SU-2022:0213-1
- SUSE-SU-2022:0334-1
- SUSE-SU-2022:1507-1
- SUSE-SU-2022:23018-1
- SUSE-SU-2023:0187-1
- SUSE-SU-2023:0326-1
- Published
- Nov 17, 2021
- Updated
- Jun 17, 2026
- EPSS
- 2.2% · 82th percentile
- CWE
- CWE-843
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
CNA vs NVD score
- NVD
- 5.0
- CNA · GitHub_M
- 3.0
- 2.0 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linuxfoundation | open container initiative distribution specification | cpe:2.3:a:linuxfoundation:open_container_initiative_distribution_specification |
| linuxfoundation | open container initiative image format specification | cpe:2.3:a:linuxfoundation:open_container_initiative_image_format_specification |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora34
- fedoraproject fedora35
- linuxfoundation open container initiative distribution specificationup to 1.0.0 inclusive
- linuxfoundation open container initiative image format specificationup to 1.0.1 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
opencontainers distribution-spec
- < 1.0.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.14 | containerd | before 1.5.8-r0 | 1.5.8-r0 |
| Alpine:v3.14 | docker | before 20.10.11-r0 | 20.10.11-r0 |
| Alpine:v3.15 | podman | before 3.4.4-r0 | 3.4.4-r0 |
| Alpine:v3.15 | skopeo | before 1.5.2-r0 | 1.5.2-r0 |
| Alpine:v3.19 | singularity | before 3.8.5-r0 | 3.8.5-r0 |
| Go | github.com/docker/docker | before 20.10.11+incompatible | 20.10.11+incompatible |
| Go | github.com/moby/moby | before 20.10.11+incompatible | 20.10.11+incompatible |
| Go | github.com/opencontainers/distribution-spec | before 1.0.1 | 1.0.1 |
| openSUSE:Leap 15.3 | conmon | before 2.0.30-150300.8.3.1 | 2.0.30-150300.8.3.1 |
| openSUSE:Leap 15.3 | containerd | before 1.4.12-60.1 | 1.4.12-60.1 |
| openSUSE:Leap 15.3 | docker | before 20.10.12_ce-159.1 | 20.10.12_ce-159.1 |
| openSUSE:Leap 15.3 | docker-kubic | before 20.10.12_ce-159.1 | 20.10.12_ce-159.1 |
| openSUSE:Leap 15.3 | libcontainers-common | before 20210626-150300.8.3.1 | 20210626-150300.8.3.1 |
| openSUSE:Leap 15.3 | libseccomp | before 2.5.3-150300.10.5.1 | 2.5.3-150300.10.5.1 |
| openSUSE:Leap 15.3 | podman | before 3.4.4-150300.9.3.2 | 3.4.4-150300.9.3.2 |
| openSUSE:Leap 15.3 | singularity | before 3.8.5-bp153.2.10.1 | 3.8.5-bp153.2.10.1 |
| openSUSE:Leap 15.6 | umoci | before 0.5.0-150000.3.15.1 | 0.5.0-150000.3.15.1 |
| openSUSE:Leap Micro 5.2 | podman | before 4.3.1-150300.9.15.1 | 4.3.1-150300.9.15.1 |
| openSUSE:Leap Micro 5.3 | podman | before 4.3.1-150400.4.11.1 | 4.3.1-150400.4.11.1 |
| openSUSE:Tumbleweed | containerd | before 1.4.12-1.1 | 1.4.12-1.1 |
| openSUSE:Tumbleweed | docker | before 20.10.11_ce-1.1 | 20.10.11_ce-1.1 |
| openSUSE:Tumbleweed | podman | before 3.4.4-1.1 | 3.4.4-1.1 |
| openSUSE:Tumbleweed | singularity | before 3.8.5-1.1 | 3.8.5-1.1 |
| openSUSE:Tumbleweed | umoci | before 0.5.0-1.1 | 0.5.0-1.1 |
+96
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:containerd | 1.5.8-r0 · Alpine:v3.14 | Package registry (OSV) |
| alpine:docker | 20.10.11-r0 · Alpine:v3.14 | Package registry (OSV) |
| alpine:podman | 3.4.4-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:singularity | 3.8.5-r0 · Alpine:v3.19 | Package registry (OSV) |
| alpine:skopeo | 1.5.2-r0 · Alpine:v3.15 | Package registry (OSV) |
| Go:github.com/docker/docker | 20.10.11+incompatible | Package registry (OSV) |
| Go:github.com/moby/moby | 20.10.11+incompatible | Package registry (OSV) |
| Go:github.com/opencontainers/distribution-spec | 1.0.1 | Package registry (OSV) |
| opensuse:conmon | 2.0.30-150300.8.3.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:containerd | 1.4.12-60.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:docker | 20.10.12_ce-159.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:docker-kubic | 20.10.12_ce-159.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:libcontainers-common | 20210626-150300.8.3.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:libseccomp | 2.5.3-150300.10.5.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:podman | 4.3.1-150400.4.11.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:singularity | 3.8.5-bp153.2.10.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:umoci | 0.5.0-150000.3.15.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:coreos-installer | 0:0.12.0-1.rhaos4.10.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:coreos-installer-bootinfra | 0:0.12.0-1.rhaos4.10.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:coreos-installer-bootinfra-debuginfo | 0:0.12.0-1.rhaos4.10.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:coreos-installer-debuginfo | 0:0.12.0-1.rhaos4.10.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:coreos-installer-debugsource | 0:0.12.0-1.rhaos4.10.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:cri-o | 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 · Red Hat:openshift:4.10::el7 | Package registry (OSV) |
| red hat:cri-o-debuginfo | 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 · Red Hat:openshift:4.10::el7 | Package registry (OSV) |
| red hat:cri-o-debugsource | 0:1.23.1-9.rhaos4.10.gitbdffb9a.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:jenkins | 0:2.319.2.1643288987-1.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:jenkins-2-plugins | 0:4.10.1643404185-1.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:openshift | 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el7 · Red Hat:openshift:4.10::el7 | Package registry (OSV) |
| red hat:openshift-clients | 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el7 · Red Hat:openshift:4.10::el7 | Package registry (OSV) |
| rocky linux:cockpit-podman | 0:53-1.module+el8.7.0+1078+e72fcd4f · Rocky Linux:8 | Package registry (OSV) |
+20
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0100 · Feb 21, 2023(OpenShift Güvenlik Güncellemesi)
- TR-22-0369 · May 20, 2022(RedHat Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923
- github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3TUZNDAH2B26VPBK342UC3BHZNLBUXGX/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4334HT7AZPLWNYHW4ARU6JBUF3VZJPZN/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/A2RRFNTMFYKOTRKD37F5ANMCIO3GGJML/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DX63GRWFEI5RVMYV6XLMCG4OHPWZML27/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RZTO6N55WHKHIZI4IMLY2QFBPMVTAERM/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SQBCYJUIM5GVCMFUPRWKRZNXMMI5EFA4/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T4OJ764CKKCWCVONHD4YXTGR7HZ7LRUV/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YIGVQWOA5XXCQXEOOKZX4CDAGLBDRPRX/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.