Skip to content
Fencer Intel
medium 6.5

CVE-2022-1706 json

Ignition config accessible to unprivileged software on VMware

published 4y ago modified 4mo ago also GHSA-hj57-j5cw-2mwp , GO-2022-0451 , EUVD-2022-4168

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/coreos/ignition/v2 2.14.0
  • go github.com/coreos/ignition 2.14.0
  • redhat ignition 2.14.0
  • ignition Debian 14, Debian 13, Debian 12 2.14.0+ds1-1

debian advisories DEBIAN-CVE-2022-1706

  • crit openshift 4.11 3.15-4.rhaos4.11.el8
  • criu openshift 4.11 3.15-4.rhaos4.11.el8
  • crun openshift 4.11 1.4.2-1.rhaos4.11.el8
  • runc openshift 4.11 3:1.1.2-1.rhaos4.11.el8
  • cri-o openshift 4.11 1.24.1-11.rhaos4.11.gitb0d2ef3.el8
  • butane openshift 4.11 0.15.0-1.rhaos4.11.el8
  • conmon openshift 4.11 2:2.1.2-2.rhaos4.11.el8
  • podman openshift 4.11 2:4.0.2-6.rhaos4.11.el8

red hat advisories RHSA-2022:5068RHSA-2022:8126

  • systemd-presets-common-SUSE SLE Module for Basesystem 15 SP4, SLE Module for Basesystem 15 SP3, SLE Micro 5.2 +4 more 15-150100.8.17.1
  • ignition SLE Micro 5.1 2.14.0-150300.4.7.1
  • ignition SLE Micro 5.2, openSUSE Leap Micro 5.2 2.14.0-150300.6.7.1

suse advisories SUSE-SU-2022:2866-2SUSE-SU-2022:2866-1SUSE-SU-2022:2350-1SUSE-SU-2022:2349-2SUSE-SU-2022:2349-1

  • ignition AlmaLinux 9 2.14.0-1.el9

almalinux advisories ALSA-2022:8126

  • ignition Rocky Linux 9 2.14.0-1.el9

rocky linux advisories RLSA-2022:8126

Is CVE-2022-1706 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-1706 updated cvss 7.5

ignition: configs are accessible from unprivileged containers in VMs running on VMware products

  • Red Hat Enterprise Linux AppStream (v. 9) ignition 2.14.0-1.el9
    fixed: vendor fix “Possible Workaround: It is not recommended to put secrets in the Ignition config.” RHSA-2022:8126
  • Red Hat OpenShift Container Platform 4.11 ignition 2.14.0-3.rhaos4.11.el8, ignition-validate 2.14.0-3.rhaos4.11.el8
    fixed: vendor fix “Possible Workaround: It is not recommended to put secrets in the Ignition config.” RHSA-2022:5068
  • Red Hat Ironic content for Red Hat OpenShift Container Platform 4.11 pysnmp 4.4.8-3.el8, pyparsing 2.3.1-2.el8, libsodium 1.0.16-5.el8, python-pbr 5.5.1-2.el8, python-yappi 1.0-3.el8, python-amqp 2.5.2-8.el8, +273 more Red Hat OpenShift Container Platform 4.11 buildah 1.23.4-2.el8, haproxy 2.2.24-1.el8, haproxy22 2.2.24-1.el8, cri-tools 1.24.2-4.1.el8, crit 3.15-4.rhaos4.11.el8, criu 3.15-4.rhaos4.11.el8, +59 more
    not affected: vulnerable code not present “Possible Workaround: It is not recommended to put secrets in the Ignition config.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:P/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/coreos/ignition/v2
<2.14.0
2.14.0
go github.com/coreos/ignition
<2.14.0
all versions
2.14.0

Affected products

  • n/a coreos/ignition

Classification

Weakness
  • CWE-863 Incorrect Authorization
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-921 Storage of Sensitive Data in a Mechanism without Access Control

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.