Ignition config accessible to unprivileged software on VMware
coreos/ignition
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/coreos/ignition/v2 Go |
|
|
| github.com/coreos/ignition Go |
|
|
coreos/ignition
| Product | Affected | Fixed in |
|---|---|---|
| github.com/coreos/ignition/v2 Go |
|
|
| github.com/coreos/ignition Go |
|
|
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.
From the CVE record · redhat
Ignition configs can be accessed from unprivileged containers in VMs running on VMware products. If a config contains secrets, an attacker with access to an unprivileged container can read them; the input does not specify a user-interaction requirement.
Check environments running Ignition in VMware VMs, especially those using Go packages github.com/coreos/ignition/v2 or github.com/coreos/ignition before 2.14.0.