CVE-2021-20319: An improper signature verification vulnerability was found in coreos-installer.
Noroxi assessment
Priority: Monitor (action score 31/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: 0.51% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: coreos-installer (crates.io) 0.10.1; cri-o (Red Hat:openshift:4.10::el7) 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7; cri-o-debuginfo (Red Hat:openshift:4.10::el7) 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7.
Low priority for now. Upgrade to coreos-installer (crates.io) 0.10.1; cri-o (Red Hat:openshift:4.10::el7) 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7; cri-o-debuginfo (Red Hat:openshift:4.10::el7) 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 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
An improper signature verification vulnerability was found in coreos-installer. A specially crafted gzip installation image can bypass the image signature verification and as a consequence can lead to the installation of unsigned content. An attacker able to modify the original installation image can write arbitrary data, and achieve full access to the node being installed.
- Published
- Mar 4, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- CWE-347
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
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.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| redhat | coreos-installer | cpe:2.3:a:redhat:coreos-installer |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a coreos-installer
- Affects coreos-installer before v0.10.1, Fixed in v0.10.1.affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat coreos-installerbefore 0.10.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| crates.io | coreos-installer | from 0.0.0-0 · before 0.10.1 | 0.10.1 |
| crates.io | coreos-installer | before 0.10.1 | 0.10.1 |
| Red Hat:openshift:4.10::el7 | cri-o | before 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 | 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 |
| Red Hat:openshift:4.10::el7 | cri-o-debuginfo | before 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 | 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 |
| Red Hat:openshift:4.10::el7 | openshift | before 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el7 | 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el7 |
| Red Hat:openshift:4.10::el7 | openshift-clients | before 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el7 | 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el7 |
| Red Hat:openshift:4.10::el7 | openshift-clients-redistributable | before 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el7 | 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el7 |
| Red Hat:openshift:4.10::el7 | openshift-hyperkube | before 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el7 | 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el7 |
| Red Hat:openshift:4.10::el8 | coreos-installer | before 0:0.12.0-1.rhaos4.10.el8 | 0:0.12.0-1.rhaos4.10.el8 |
| Red Hat:openshift:4.10::el8 | coreos-installer-bootinfra | before 0:0.12.0-1.rhaos4.10.el8 | 0:0.12.0-1.rhaos4.10.el8 |
| Red Hat:openshift:4.10::el8 | coreos-installer-bootinfra-debuginfo | before 0:0.12.0-1.rhaos4.10.el8 | 0:0.12.0-1.rhaos4.10.el8 |
| Red Hat:openshift:4.10::el8 | coreos-installer-debuginfo | before 0:0.12.0-1.rhaos4.10.el8 | 0:0.12.0-1.rhaos4.10.el8 |
| Red Hat:openshift:4.10::el8 | coreos-installer-debugsource | before 0:0.12.0-1.rhaos4.10.el8 | 0:0.12.0-1.rhaos4.10.el8 |
| Red Hat:openshift:4.10::el8 | cri-o | before 0:1.23.1-9.rhaos4.10.gitbdffb9a.el8 | 0:1.23.1-9.rhaos4.10.gitbdffb9a.el8 |
| Red Hat:openshift:4.10::el8 | cri-o-debuginfo | before 0:1.23.1-9.rhaos4.10.gitbdffb9a.el8 | 0:1.23.1-9.rhaos4.10.gitbdffb9a.el8 |
| Red Hat:openshift:4.10::el8 | cri-o-debugsource | before 0:1.23.1-9.rhaos4.10.gitbdffb9a.el8 | 0:1.23.1-9.rhaos4.10.gitbdffb9a.el8 |
| Red Hat:openshift:4.10::el8 | jenkins | before 0:2.319.2.1643288987-1.el8 | 0:2.319.2.1643288987-1.el8 |
| Red Hat:openshift:4.10::el8 | jenkins-2-plugins | before 0:4.10.1643404185-1.el8 | 0:4.10.1643404185-1.el8 |
| Red Hat:openshift:4.10::el8 | openshift | before 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el8 | 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el8 |
| Red Hat:openshift:4.10::el8 | openshift-clients | before 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el8 | 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el8 |
| Red Hat:openshift:4.10::el8 | openshift-clients-redistributable | before 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el8 | 0:4.10.0-202202160023.p0.gf93da17.assembly.stream.el8 |
| Red Hat:openshift:4.10::el8 | openshift-hyperkube | before 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el8 | 0:4.10.0-202202250816.p0.ge419edf.assembly.stream.el8 |
| Red Hat:openshift:4.6::el8 | coreos-installer | before 0:0.6.0-4.rhaos4.6.el8 | 0:0.6.0-4.rhaos4.6.el8 |
| Red Hat:openshift:4.6::el8 | coreos-installer-bootinfra | before 0:0.6.0-4.rhaos4.6.el8 | 0:0.6.0-4.rhaos4.6.el8 |
+18
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3917A flaw was found in the coreos-installer, where it writes the Ignition config to the target system with world-readable access permissions.22Monitor
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 |
|---|---|---|
| crates.io:coreos-installer | 0.10.1 | Package registry (OSV) |
| red hat:coreos-installer | 0:0.9.0-7.rhaos4.8.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
| red hat:coreos-installer-bootinfra | 0:0.9.0-7.rhaos4.8.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
| red hat:coreos-installer-bootinfra-debuginfo | 0:0.9.0-7.rhaos4.8.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
| red hat:coreos-installer-debuginfo | 0:0.9.0-7.rhaos4.8.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
| red hat:coreos-installer-debugsource | 0:0.9.0-7.rhaos4.8.el8 · Red Hat:openshift:4.8::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) |
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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.