Skip to content

Duplicate advisory: Configuration exposure in github.com/coreos/ignition

Moderate severity GitHub Reviewed Published May 18, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023
Withdrawn This advisory was withdrawn on Jun 8, 2022

Package

gomod github.com/coreos/ignition/v2 (Go)

Affected versions

< 2.14.0

Patched versions

2.14.0

Description

Duplicate Advisory

This advisory is a duplicate of GHSA-hj57-j5cw-2mwp. This link is preserved to maintain external references.

Original 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.

References

Published by the National Vulnerability Database May 17, 2022
Published to the GitHub Advisory Database May 18, 2022
Reviewed May 25, 2022
Withdrawn Jun 8, 2022
Last updated Jan 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-mjqc-5c9x-xfcc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.