First published: Wed May 04 2022(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/ignition | <0:2.14.0-1.el9 | 0:2.14.0-1.el9 |
redhat/ignition | <0:2.14.0-3.rhaos4.11.el8 | 0:2.14.0-3.rhaos4.11.el8 |
Redhat Ignition | <2.14.0 | |
Redhat Openshift Container Platform | =4.0 | |
Redhat Enterprise Linux | =9.0 | |
Fedoraproject Fedora | =34 | |
Fedoraproject Fedora | =35 | |
Fedoraproject Fedora | =36 |
Possible Workaround: It is not recommended to put secrets in the Ignition config.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2022-1706.
CVE-2022-1706 has a severity level of high.
This vulnerability can be exploited by unprivileged containers in VMs running on VMware products to access ignition configs.
The highest threat from CVE-2022-1706 is to data confidentiality.
To fix the Ignition vulnerability, update to version 2.14.0 or higher.