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. A…
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Mar 4, 2022, 5:05:50 PM
dateUpdated: Aug 3, 2024, 5:37:23 PM
5 related source bulletins · separate from aliases
RHSA-2021:4008: Red Hat Security Advisory: OpenShift Container Platform 4.6.49 security update
CVE-2021-20319
RHSA-2021:3934: Red Hat Security Advisory: OpenShift Container Platform 4.9.4 packages and security update
CVE-2021-20319
RHSA-2021:3926: Red Hat Security Advisory: OpenShift Container Platform 4.8.17 security and bug fix update
CVE-2021-20319
RHSA-2021:3930: Red Hat Security Advisory: OpenShift Container Platform 4.7.36 security and bug fix update
CVE-2021-20319
RHSA-2022:0055: Red Hat Security Advisory: OpenShift Container Platform 4.10.3 bug fix and security update
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-347
Original publisher date fields
published: 2022-03-04T18:15:08.060
lastModified: 2026-06-17T03:33:39.947
1 source CPE criteria · context only
cpe:2.3:a:redhat:coreos-installer:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.