CVE-2022-1706: Github.com/coreos/ignition/v2 Ignition Config Accessible To Unprivileged Vulnerability

MODERATE
Advisory Identifier: GHSA-hj57-j5cw-2mwp
CVSS 6.5
CWE-921 CWE-200 CWE-863
Published
Advisory Summary

CVE-2022-1706 is a MODERATE (CVSS 6.5) ignition config accessible to unprivileged vulnerability (CWE-921: Storage of Sensitive Data in a Mechanism without Access Control) affecting Github.com/coreos/ignition/v2 libraries in the Go ecosystem. The issue involves ignition config accessible to unprivileged software on vmware. Remediation is available by upgrading affected packages to version 2.14.0.

CVE-2022-1706 at a Glance

CVE Identifier CVE-2022-1706
GHSA Identifier GHSA-hj57-j5cw-2mwp
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-921: Storage of Sensitive Data in a Mechanism without Access Control
Affected Product Github.com/coreos/ignition/v2
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2022-1706

To remediate this vulnerability, upgrade all affected Github.com/coreos/ignition/v2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/coreos/ignition/v2 fixed: 2.14.0
Upgrade github.com/coreos/ignition/v2 to 2.14.0
github.com/coreos/ignition fixed: 2.14.0
Upgrade github.com/coreos/ignition to 2.14.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/coreos/ignition/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2022-1706, inspect your project dependencies for Github.com/coreos/ignition/v2:

inspect dependencies for github.com/coreos/ignition/v2

Analyze the terminal output to locate any version of Github.com/coreos/ignition/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.14.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-921: Storage of Sensitive Data in a Mechanism without Access Control, where the product stores sensitive information in a file system or device that does not have built-in access control. In Github.com/coreos/ignition/v2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Unprivileged software in VMware VMs, including software running in unprivileged containers, can retrieve an Ignition config stored in a hypervisor guestinfo variable or OVF environment. If the Ignition config contains secrets, this can result in the compromise of sensitive information. ### Patches Ignition 2.14.0 and later [adds](https://github.com/coreos/ignition/pull/1350) a new systemd service, `ignition-delete-config.service`, that deletes the Ignition config from supported hypervisors (currently VMware and VirtualBox) during the first boot. This ensures that unprivileged software cannot retrieve the Ignition config from the hypervisor. If you have external tooling that requires the Ignition config to remain accessible in VM metadata after provisioning, and your Ignition config does not include sensitive information, you can prevent Ignition 2.14.0 and later from deleting the config by masking `ignition-delete-config.service`. For example: ```json { "ignition": { "version": "3.0.0" }, "systemd": { "units": [ { "name": "ignition-delete-config.service", "mask": true } ] } } ``` ### Workarounds [Avoid storing secrets](https://coreos.github.io/ignition/operator-notes/#secrets) in Ignition configs. In addition to VMware, many cloud platforms allow unprivileged software in a VM to retrieve the Ignition config from a networked cloud metadata service. While platform-specific mitigation is possible, such as firewall rules that prevent access to the metadata service, it's best to store secrets in a dedicated platform such as [Hashicorp Vault](https://www.vaultproject.io/). ### Advice to Linux distributions Linux distributions that ship Ignition should ensure the new `ignition-delete-config.service` is installed and enabled by default. In addition, we recommend shipping a service similar to `ignition-delete-config.service` that runs when existing machines are upgraded, similar to the one in https://github.com/coreos/fedora-coreos-config/pull/1738. Consider giving your users advance notice of this change, and providing instructions for masking `ignition-delete-config.service` on existing nodes if users have tooling that requires the Ignition config to remain accessible in VM metadata. ### References For more information, see #1300 and #1350. ### For more information If you have any questions or comments about this advisory, [open an issue in Ignition](https://github.com/coreos/ignition/issues/new/choose) or email the CoreOS [development mailing list](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/).

CVE-2022-1706 Affected Github.com/coreos/ignition/v2 Versions

2 component(s)
Fixed Versions:
2.14.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/coreos/ignition/v2
Go
< 2.14.0
2.14.0
github.com/coreos/ignition
Go
< 2.14.0
2.14.0

References

Frequently Asked Questions

What is CVE-2022-1706?
CVE-2022-1706 is a security vulnerability in Github.com/coreos/ignition/v2 involving Ignition config accessible to unprivileged software on VMware under CWE-921: Storage of Sensitive Data in a Mechanism without Access Control.
Which Github.com/coreos/ignition/v2 versions are affected?
Affected versions include releases prior to 2.14.0 across affected packages: github.com/coreos/ignition/v2, github.com/coreos/ignition.
What version fixes CVE-2022-1706?
Upgrading to 2.14.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/coreos/ignition/v2 affected?
Yes, github.com/coreos/ignition/v2 is affected in releases prior to 2.14.0. Upgrade your dependency to 2.14.0 or later.
Is github.com/coreos/ignition affected?
Yes, github.com/coreos/ignition is affected in releases prior to 2.14.0. Upgrade your dependency to 2.14.0 or later.
What is the CVSS score of CVE-2022-1706?
CVE-2022-1706 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2022-1706?
CVE-2022-1706 is classified under CWE-921: Storage of Sensitive Data in a Mechanism without Access Control (The product stores sensitive information in a file system or device that does not have built-in access control.).
How can I check Go dependencies for CVE-2022-1706?
Run the dependency tree command: 'inspect dependencies for github.com/coreos/ignition/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hj57-j5cw-2mwp",
  "modified" : "2026-03-11T19:49:57Z",
  "published" : "2022-05-25T19:37:37Z",
  "aliases" : [ "CVE-2022-1706" ],
  "summary" : "Ignition config accessible to unprivileged software on VMware",
  "details" : "### Impact\nUnprivileged software in VMware VMs, including software running in unprivileged containers, can retrieve an Ignition config stored in a hypervisor guestinfo variable or OVF environment.  If the Ignition config contains secrets, this can result in the compromise of sensitive information.\n\n### Patches\nIgnition 2.14.0 and later [adds](https://github.com/coreos/ignition/pull/1350) a new systemd service, `ignition-delete-config.service`, that deletes the Ignition config from supported hypervisors (currently VMware and VirtualBox) during the first boot.  This ensures that unprivileged software cannot retrieve the Ignition config from the hypervisor.\n\nIf you have external tooling that requires the Ignition config to remain accessible in VM metadata after provisioning, and your Ignition config does not include sensitive information, you can prevent Ignition 2.14.0 and later from deleting the config by masking `ignition-delete-config.service`.  For example:\n\n```json\n{\n  \"ignition\": {\n    \"version\": \"3.0.0\"\n  },\n  \"systemd\": {\n    \"units\": [\n      {\n        \"name\": \"ignition-delete-config.service\",\n        \"mask\": true\n      }\n    ]\n  }\n}\n```\n\n### Workarounds\n[Avoid storing secrets](https://coreos.github.io/ignition/operator-notes/#secrets) in Ignition configs. In addition to VMware, many cloud platforms allow unprivileged software in a VM to retrieve the Ignition config from a networked cloud metadata service. While platform-specific mitigation is possible, such as firewall rules that prevent access to the metadata service, it's best to store secrets in a dedicated platform such as [Hashicorp Vault](https://www.vaultproject.io/).\n\n### Advice to Linux distributions\nLinux distributions that ship Ignition should ensure the new `ignition-delete-config.service` is installed and enabled by default.\n\nIn addition, we recommend shipping a service similar to `ignition-delete-config.service` that runs when existing machines are upgraded, similar to the one in https://github.com/coreos/fedora-coreos-config/pull/1738. Consider giving your users advance notice of this change, and providing instructions for masking `ignition-delete-config.service` on existing nodes if users have tooling that requires the Ignition config to remain accessible in VM metadata.\n\n### References\nFor more information, see #1300 and #1350.\n\n### For more information\nIf you have any questions or comments about this advisory, [open an issue in Ignition](https://github.com/coreos/ignition/issues/new/choose) or email the CoreOS [development mailing list](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/coreos/ignition/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.14.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/coreos/ignition"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.14.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.35.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/coreos/ignition/security/advisories/GHSA-hj57-j5cw-2mwp"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/coreos/ignition/issues/1300"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/coreos/ignition/pull/1350"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/coreos/ignition"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-863", "CWE-921" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-05-25T19:37:37Z",
    "nvd_published_at" : null
  }
}