# CVE-2022-3287: Information disclosure in fwupd

> Local attackers can read BMC operator passwords from a world-readable configuration file in fwupd, leading to credential exposure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** ALSA-2023:7189, DEBIAN-CVE-2022-3287, GHSA-7qqr-wwjq-98v6, RHSA-2023:7189, RHSA-2024:1106, RHSA-2024:1403, RLSA-2023:7189, UBUNTU-CVE-2022-3287, openSUSE-SU-2024:12438-1

## What is CVE-2022-3287?

CVE-2022-3287 is a medium-severity vulnerability in fwupd, published on 28 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When creating an OPERATOR user account on the BMC, the redfish plugin saved the auto-generated password to /etc/fwupd/redfish.conf without proper restriction, allowing any user on the system to read the same configuration file.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-256 (Plaintext Storage of a Password)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fwupd` | AlmaLinux:8 | All versions | 1.7.8-2.el8 |
| `fwupd-devel` | AlmaLinux:8 | All versions | 1.7.8-2.el8 |
| `fwupd` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.7.8-2.el8 |
| `fwupd-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.7.8-2.el8 |
| `fwupd-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.7.8-2.el8 |
| `fwupd-tests-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.7.8-2.el8 |
| `fwupd-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.8-2.el8 |
| `fwupd-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.8-2.el8 |
| `fwupd-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.8-2.el8 |
| `fwupd-tests-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.8-2.el8 |
| `fwupd` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:1.7.4-3.el8_6 |
| `fwupd-debuginfo` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:1.7.4-3.el8_6 |
| `fwupd-debugsource` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:1.7.4-3.el8_6 |
| `fwupd-tests-debuginfo` | Red Hat:rhel_eus:8.6::baseos | All versions | 0:1.7.4-3.el8_6 |
| `fwupd-debuginfo` | Red Hat:rhel_eus:8.6::crb | All versions | 0:1.7.4-3.el8_6 |
| `fwupd-debugsource` | Red Hat:rhel_eus:8.6::crb | All versions | 0:1.7.4-3.el8_6 |
| `fwupd-devel` | Red Hat:rhel_eus:8.6::crb | All versions | 0:1.7.4-3.el8_6 |
| `fwupd-tests-debuginfo` | Red Hat:rhel_eus:8.6::crb | All versions | 0:1.7.4-3.el8_6 |
| `fwupd` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:1.7.8-2.el8_8 |
| `fwupd-debuginfo` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:1.7.8-2.el8_8 |
| `fwupd-debugsource` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:1.7.8-2.el8_8 |
| `fwupd-tests-debuginfo` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:1.7.8-2.el8_8 |
| `fwupd-debuginfo` | Red Hat:rhel_eus:8.8::crb | All versions | 0:1.7.8-2.el8_8 |
| `fwupd-debugsource` | Red Hat:rhel_eus:8.8::crb | All versions | 0:1.7.8-2.el8_8 |
| `fwupd-devel` | Red Hat:rhel_eus:8.8::crb | All versions | 0:1.7.8-2.el8_8 |
| `fwupd-tests-debuginfo` | Red Hat:rhel_eus:8.8::crb | All versions | 0:1.7.8-2.el8_8 |
| `fwupd` | Rocky Linux:8 | All versions | 0:1.7.8-2.el8.rocky.0.1 |
| `fwupd` | openSUSE:Tumbleweed | All versions | 1.8.6-1.1 |

Products: Fwupd Fwupd.

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

Apply the vendor's patch.

## Is CVE-2022-3287 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3287 is a medium-severity vulnerability in fwupd, published on 28 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3287 in the wild and no public exploit code.

Affected product: fwupd. 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-3287/ (Markdown: https://insights.sbomify.com/CVE-2022-3287/index.md)
```

## Sources

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

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