CVE-2024-31916
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 · uneditedIBM OpenBMC FW1050.00 through FW1050.10 BMCWeb HTTPS server component could disclose sensitive URI content to an unauthorized actor that bypasses authentication channels. IBM X-ForceID: 290026.
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 confidenceIBM OpenBMC FW1050.00 through FW1050.10 contains a vulnerability in the BMCWeb HTTPS server component where sensitive URI content can be disclosed to unauthorized actors who bypass authentication channels. This allows information disclosure of URI paths that should require authentication.
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>= fw1050.00, <= fw1050.10CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 versionRetrieve the installed BMC firmware version via IPMI command (ipmitool mc info), Redfish API (GET /redfish/v1/Managers/1), or BMC web interface. Compare the firmware version string to the affected range.Affected if The firmware version is FW1050.00 through FW1050.10 (inclusive).
-
Confirm BMCWeb HTTPS service is activeVerify that the BMCWeb service is running on the BMC. This can be done via Redfish (GET /redfish/v1/Managers/1/NetworkProtocol) or by attempting to access the BMC HTTPS web interface.Affected if BMCWeb HTTPS server is enabled and accessible on the BMC.
-
Assess network accessibility of BMC management interfaceDetermine if the BMC HTTP/HTTPS management interface is exposed to untrusted networks. Check network configuration, firewall rules, or attempt outbound connection probes to port 443 from an untrusted network segment.Affected if The BMC management interface (HTTPS) is reachable from network segments where unauthorized users could attempt URI access.
You are affected if your OpenBMC firmware version falls within FW1050.00 to FW1050.10 and the BMCWeb HTTPS server is network-accessible, allowing potential unauthorized disclosure of authenticated URI paths.
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 dataApply the vendor-supplied firmware update (FW1050.11 or later) to address the BMCWeb authentication bypass in the OpenBMC firmware. If no patch is available, restrict network access to the BMC management interface and monitor for unauthorized access attempts.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31916 — 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-2024-31916 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