CVE-2022-3675 json
Fedora CoreOS supports setting a GRUB bootloader password using a Butane config.
published 2022-11-03 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-43034
- cvss
- 2.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
Fedora CoreOS supports setting a GRUB bootloader password using a Butane config. When this feature is enabled, GRUB requires a password to access the GRUB command-line, modify kernel command-line arguments, or boot non-default OSTree deployments. Recent Fedora CoreOS releases have a misconfiguration which allows booting non-default OSTree deployments without entering a password. This allows someone with access to the GRUB menu to boot into an older version of Fedora CoreOS, reverting any security fixes that have recently been applied to the machine. A password is still required to modify kernel command-line arguments and to access the GRUB command line.
Patch / fix
- Fedora Project CoreOS next 37.20221031.1.0, stable 36.20221014.3.0, testing 36.20221030.2.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Fedora Project CoreOS
Classification
References
-
lists.fedoraproject.org
/archives/list/coreos-status@lists.fedoraproject.org/thread/NHUCNH5Y4UH5DPUCXISYXXVA563TLFEJ/
release-notes, mailing-list, vendor-advisory
-
docs.fedoraproject.org
/en-US/fedora-coreos/grub-password/
related, vendor-advisory
-
github.com
/coreos/fedora-coreos-tracker/issues/1333
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2022-3675
- NVD CVE-2022-3675
Fencer Vulns 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.