CVE-2022-29494
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 · uneditedImproper input validation in firmware for OpenBMC in some Intel(R) platforms before versions egs-0.91-179 and bhs-04-45 may allow an authenticated user to potentially enable denial of service via network access.
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 confidenceImproper input validation in OpenBMC firmware on certain Intel platforms allows an authenticated attacker to cause denial of service via network access by sending specially crafted input that the software fails to validate properly before processing.
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< wht-1.01-61_0.72< egs-0.91-179CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 OpenBMC firmware versionRun `ipmitool mc info` or query the Redfish endpoint `/redfish/v1/Managers/1` to retrieve the BMC firmware versionAffected if The installed version is lower than egs-0.91-179 or wht-1.01-61_0.72
-
Confirm the BMC platform variantCheck the BMC firmware variant name (e.g., egs, wht) from the version string or via `ipmitool raw` commands to the BMCAffected if The platform variant matches one of the affected branches (wht or egs)
-
Verify network management interfaces are enabledCheck if web-based management (bmcweb) or IPMI over LAN is enabled via Redfish at `/redfish/v1/Managers/1/NetworkProtocol` or using `ipmitool lan print`Affected if HTTP/HTTPS web interfaces or IPMI over LAN are active and reachable on the network
You are affected if your OpenBMC firmware version is below egs-0.91-179 or wht-1.01-61_0.72 on the Intel platforms and network management interfaces are enabled.
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.
dbcve · scopedUpdate OpenBMC firmware to version egs-0.91-179, bhs-04-45, or later to remediate the input validation flaw.
egs-0.91-179 (for egs-based platforms) or bhs-04-45 (for bhs-based platforms)
- Identify the specific Intel(R) platform running OpenBMC to determine the correct firmware branch
- Check current OpenBMC version using 'obmcutil --vmm' or via web UI/BMC IP interface
- For Intel platforms using the 'egs' branch: upgrade to version egs-0.91-179 or later
- For Intel platforms using the 'bhs' branch: upgrade to version bhs-04-45 or later
- Obtain the firmware update from Intel's support website or authorized distribution channels
- Apply the firmware update using standard OpenBMC update procedures (typically via BMC web UI or 'fw_update' utility)
- After reboot, verify the new version is installed by checking the BMC version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29494 — 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-29494 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