# CVE-2022-3675: Fedora CoreOS supports setting a GRUB bootloader password using a Butane config.


- **Severity:** Low 2.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2022
- **Updated:** 2 May 2025
- **Also known as:** GHSA-747q-wq4p-22g3

## What is CVE-2022-3675?

CVE-2022-3675 is a low-severity vulnerability in Fedora Project CoreOS, published on 3 Nov 2022. 

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-3675?

It affects 1 product.


Products: Redhat Fedora Coreos.

## How do I fix CVE-2022-3675?

No fix has been published for CVE-2022-3675 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-3675 being exploited?

There is no known exploitation of CVE-2022-3675 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3675 and fix it if it is affected.

What it is: CVE-2022-3675 is a low-severity vulnerability in Fedora Project CoreOS, published on 3 Nov 2022. 
Exploitation: There is no known exploitation of CVE-2022-3675 in the wild and no public exploit code.

Affected product: Fedora Project CoreOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3675/ (Markdown: https://insights.sbomify.com/CVE-2022-3675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3675
- OSV: https://osv.dev/vulnerability/CVE-2022-3675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3675/
Summaries are generated and may contain mistakes; the official description above is the record.