CVE-2024-35124
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 the combination of the OpenBMC's FW1050.00 through FW1050.10, FW1030.00 through FW1030.50, and FW1020.00 through FW1020.60 default password and session management allow an attacker to gain administrative access to the BMC. IBM X-Force ID: 290674.
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 confidenceOpenBMC firmware versions FW1050.00-10, FW1030.00-50, and FW1020.00-60 contain a default password vulnerability combined with weak session management that allows unauthenticated attackers to gain administrative/root access to the Baseboard Management Controller via the web interface or IPMI. The default credentials (typically root/root) combined with improper session token validation enables full compromise of the BMC.
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>= fw1020.00, <= fw1020.60>= fw1030.00, <= fw1030.50>= 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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 access BMC web interface to view firmware version informationAffected if Firmware version falls within fw1020.00-fw1020.60, fw1030.00-fw1030.50, or fw1050.00-fw1050.10
-
Verify default root credentials statusAttempt to authenticate to the BMC web interface or via IPMI using root/root credentialsAffected if Default credentials root/root are still active and grant administrative access
-
Check for weak session token validationInspect BMC session configuration or attempt to reuse/replay session tokens after logout via web UI or APIAffected if Session tokens remain valid after logout or can be reused without re-authentication
-
Determine exposure of management interfacesReview network configuration to check if BMC web interface (HTTPS/HTTP) or IPMI (port 623) is accessible from untrusted networksAffected if Web or IPMI interfaces are exposed to untrusted networks without network segmentation
-
Confirm administrative access without credential changeCheck if the BMC has been provisioned with non-default administrative passwords or if factory default credentials remain unchangedAffected if BMC still uses factory default administrative passwords
A system is affected if it runs OpenBMC firmware within the specified version ranges AND still has default credentials (root/root) active AND the management interfaces are accessible.
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 dataImmediately change all default credentials on affected BMCs and update to patched firmware versions when available. Disable remote administrative access if not required and implement network segmentation to limit BMC exposure.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35124 — 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-35124 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