Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-2809: A vulnerability in bmcweb of OpenBMC Project allows user to cause denial of service

48
This month
HIGH 8.2REMOTEUPGRADE

CVE-2022-2809 is a high-severity flaw (CVSS 8.2) affecting openbmc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability in bmcweb of OpenBMC Project allows user to cause denial of service. When fuzzing the multipart_parser code using AFL++ with address sanitizer enabled to find smallest memory corruptions possible. It detected problem in how multipart_parser handles unclosed http headers. If long enough http header is passed in the multipart form without colon there is one byte overwrite on heap. It can be conducted multiple times in a loop to caus

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score8.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.8% (top 44%)
CISA exploited listNo
WeaknessCWE-122, CWE-229, CWE-787
Published2022-10-27
Last modified2026-06-17
Publisher (CNA): The OpenBMC Project · Vendor: openbmc-project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

openbmc-project openbmc UPGRADE
Affected: >= 2.10.0 and <= 2.13.0
Fixed in: newer than 2.13.0
Safe to downgrade to: a release before 2.10.0
1. Check installed version
apt-cache policy openbmc || rpm -q openbmc || openbmc --version
2. UPGRADE to newer than 2.13.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade openbmc
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade openbmc
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.10.0 (Debian / Ubuntu)
apt-cache madison openbmc sudo apt install openbmc=<VERSION_BEFORE_2.10.0> sudo apt-mark hold openbmc
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list openbmc sudo dnf downgrade openbmc-<VERSION_BEFORE_2.10.0> sudo dnf versionlock add openbmc
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2809?

openbmc: upgrade to newer than 2.13.0. Exact commands for each OS are on this page.

Is CVE-2022-2809 being exploited?

CVE-2022-2809 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2809 affect?

CVE-2022-2809 affects openbmc. Severity is high (CVSS 8.2). A vulnerability in bmcweb of OpenBMC Project allows user to cause denial of service. When fuzzing the multipart_parser code using AFL++ with address sanitizer enabled to find smallest memory corruptions possible. It detected problem in how

How urgent is CVE-2022-2809?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.