Bug 2018478 (CVE-2021-3917) - CVE-2021-3917 coreos-installer: restrict access permissions on /boot/ignition{,/config.ign}
Summary: CVE-2021-3917 coreos-installer: restrict access permissions on /boot/ignition...
Alias: CVE-2021-3917
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1989544 2018889 2021210 2021285 2021286 2021287 2021288
Blocks: 2018480
TreeView+ depends on / blocked
Reported: 2021-10-29 12:51 UTC by Cedric Buissart
Modified: 2022-03-08 12:13 UTC (History)
18 users (show)

Fixed In Version: coreos-installer 0.10.0
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the coreos-installer, where it writes the Ignition config to the target system with world-readable access permissions. This flaw allows a local attacker to have read access to potentially sensitive data. The highest threat from this vulnerability is to confidentiality.
Clone Of:
Last Closed: 2021-11-30 09:52:02 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4829 0 None None None 2021-11-30 09:09:00 UTC

Description Cedric Buissart 2021-10-29 12:51:12 UTC
coreos-installer did not have sufficiently restrictive permissions on directories /boot/ignition{,/config.ign}. A local attacker could use this flaw to have read access to potentially sensitive data.

Upstream fix :

Fixed in version 0.10.0

Comment 1 Cedric Buissart 2021-11-01 08:04:54 UTC
Created rust-coreos-installer tracking bugs for this issue:

Affects: fedora-all [bug 2018889]

Comment 4 juneau 2021-11-02 15:33:05 UTC
Setting OSD "notaffected" per https://bugzilla.redhat.com/show_bug.cgi?id=1989544#c3

Comment 7 errata-xmlrpc 2021-11-30 09:08:59 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.8

Via RHSA-2021:4829 https://access.redhat.com/errata/RHSA-2021:4829

Comment 8 Product Security DevOps Team 2021-11-30 09:52:00 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.