CVE-2022-2809
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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 cause DoS.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHeap-based one-byte overflow vulnerability in bmcweb's multipart_parser. When a multipart HTTP form contains a long header without a colon (unclosed header), the parser writes one byte past the allocated heap buffer. An attacker can repeatedly trigger this to cause denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.10.0, <= 2.13.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify bmcweb versionRun 'bmcweb --version' or check package version via 'rpm -q bmcweb' or 'dpkg -l bmcweb' depending on system package managerAffected if Version falls within 2.10.0 to 2.13.0 range (or version cannot be determined but system is known to be OpenBMC between 2.10.0-2.13.0)
-
Confirm OpenBMC versionCheck /etc/os-release or run 'cat /etc/issue' or use BMC IPMI commands to query BMC firmware versionAffected if Firmware version is >= 2.10.0 and <= 2.13.0
-
Verify multipart parser is in useReview HTTP server configuration files for bmcweb (typically in /etc/bmcweb or /usr/share/bmcweb) and check for multipart/form-data handler enablmentAffected if Multipart form upload functionality is enabled in bmcweb configuration
-
Check exposed HTTP endpointsScan accessible HTTP/HTTPS ports on the BMC management interface (typically ports 80, 443, 4433) using nmap or curl to identify if bmcweb REST APIs are reachableAffected if BMC web interface is accessible over network and supports multipart form uploads (typically /api/upload/* endpoints)
-
Audit network access policiesReview firewall rules, ACLs, or network isolation settings controlling access to the BMC web interfaceAffected if BMC HTTP endpoints are accessible from untrusted networks (no IP restrictions or VPN isolation)
System is affected if running OpenBMC/bmcweb versions 2.10.0 through 2.13.0 with the multipart parser enabled and the BMC web interface accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate bmcweb to patched version. Until then, restrict multipart form uploads via firewall/ACL or disable unused HTTP endpoints to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2809 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2809 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data