CVE-2022-1706: High severity red hat ignition vulnerability
A vulnerability was found in Ignition where ignition configs are accessible from unprivileged containers in VMs running on VMware products. This issue is only relevant in user environments where the Ignition config contains secrets. The highest threat from this vulnerability is to data confidentiality. Possible workaround is to not put secrets in the Ignition config.
Other sources
A vulnerability was found in Ignition, where ignition configs are accessible from unprivileged containers in VMs running on VMware products. This issue is only relevant in user environments where the Ignition config contains secrets.
ignition configs are accessible from unprivileged containers in VMs running on VMware products. This issue is only relevant in user environments where the Ignition config contains secrets. We don't recommend putting secrets in the Ignition config, but presumably some users do it anyway.
References: https://github.com/coreos/ignition/issues/1300 https://github.com/coreos/ignition/pull/1350
— Red Hat
Affected Software
Remediation
Information
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the vulnerability ID for this Ignition vulnerability?
The vulnerability ID is CVE-2022-1706.
What is the severity level of CVE-2022-1706?
CVE-2022-1706 has a severity level of high.
How can this vulnerability be exploited?
This vulnerability can be exploited by unprivileged containers in VMs running on VMware products to access ignition configs.
What is the highest threat from CVE-2022-1706?
The highest threat from CVE-2022-1706 is to data confidentiality.
How do I fix the Ignition vulnerability?
To fix the Ignition vulnerability, update to version 2.14.0 or higher.