You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
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.
See doc/triage.md for instructions on how to triage this report.
module: github.com/coreos/ignition
package: coreos/ignition
description: |
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.
cves:
- CVE-2022-1706
links:
pr: https://github.com/coreos/ignition/pull/1350
commit: https://github.com/coreos/ignition/commit/4b70b44b430ecf8377a276e89b5acd3a6957d4ea
context:
- https://bugzilla.redhat.com/show_bug.cgi?id=2082274
- https://github.com/coreos/ignition/issues/1300
- https://github.com/coreos/ignition/issues/1315
The text was updated successfully, but these errors were encountered:
CVE-2022-1706 references github.com/coreos/ignition, which may be a Go module.
Description:
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.
Links:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: