dbcve.org
Power System E1080 \(9080 Hex\) FirmwareOperating system · Ibm

CVE-2024-45656

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
IBM Flexible Service Processor (FSP) FW860.00 through FW860.B3, FW950.00 through FW950.C0, FW1030.00 through FW1030.61, FW1050.00 through FW1050.21, and FW1060.00 through FW1060.10 has static credentials which may allow network users to gain service privileges to the FSP.

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 confidence

IBM Flexible Service Processor (FSP) firmware across multiple version ranges (FW860, FW950, FW1030, FW1050, FW1060) contains hardcoded static credentials that can be discovered and used by network attackers to authenticate and gain service-level privileges to the FSP management interface.

MitigationUpdate FSP firmware to a version beyond the vulnerable ranges (FW860.B3, FW950.C0, FW1030.61, FW1050.21, FW1060.10) or contact IBM for a patch; if immediate update is not possible, restrict network access to the FSP management ports.

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
Power System E1080 \(9080 Hex\) FirmwareOperating system
Affected:>= FW1030.00, <= FW1030.61>= FW1050.00, <= FW1050.21>= FW1060.00, <= FW1060.10
Power System L922 \(9008 22l\) FirmwareOperating system
Affected:>= FW950.00, <= FW950.C0
Power System S922 \(9009 22a\) FirmwareOperating system
Affected:>= FW950.00, <= FW950.C0
Power System S922 \(9009 22g\) FirmwareOperating system
Affected:>= FW950.00, <= FW950.C0
Power System H922 \(9223 22h\) FirmwareOperating system
Affected:>= FW950.00, <= FW950.C0
Power System H922 \(9223 22s\) FirmwareOperating system
Affected:>= FW950.00, <= FW950.C0
Power System S914 \(9009 41a\) FirmwareOperating system
Affected:>= FW950.00, <= FW950.C0
Power System S914 \(9009 41g\) FirmwareOperating system
Affected:>= FW950.00, <= FW950.C0

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the IBM Power System model
    Determine the machine type, model, and machine ID of the system. This can be obtained from the system hardware inventory, BMC/ASMI interface, or by running 'lsattr -El sys0' on AIX/Linux and checking the 'model' and 'machine_id' attributes. Look for model identifiers such as 9080, 9008-22l, 9009-22a, 9009-22g, 9223-22h, 9223-22s, 9009-41a, or 9009-41g.
    Affected if The model is one of the affected systems: E1080 (9080), L922 (9008-22l), S922 (9009-22a or 9009-22g), H922 (9223-22h or 9223-22s), or S914 (9009-41a or 9009-41g).
  2. Retrieve the FSP firmware version
    Access the Flexible Service Processor (FSP) via the Advanced System Management Interface (ASMI) or use the ASMI REST API. Navigate to FSP Overview or Firmware Version information. Alternatively, on AIX systems, run 'lsfsp' or query the FSP via the service processor interface. Record the firmware version number in the format FWxx0.xx (for example, FW1030.00, FW950.00, etc.).
    Affected if The FSP firmware is accessible and a version can be retrieved.
  3. Compare firmware version against affected ranges
    Match your identified model and firmware version to the affected version ranges: E1080: FW1030.00 through FW1030.61, FW1050.00 through FW1050.21, or FW1060.00 through FW1060.10; L922, S922 (22a/22g), H922 (22h/22s), S914 (41a/41g): FW950.00 through FW950.C0. Check if your installed version falls within these inclusive ranges.
    Affected if The installed FSP firmware version is greater than or equal to the lower bound and less than or equal to the upper bound of any affected range for your model.

A system is affected if it is an IBM Power System E1080, L922, S922, H922, or S914 model running FSP firmware within the specific version ranges listed for that model, as the hardcoded static credentials are present in those firmware versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update FSP firmware to a version beyond the vulnerable ranges (FW860.B3, FW950.C0, FW1030.61, FW1050.21, FW1060.10) or contact IBM for a patch; if immediate update is not possible, restrict network access to the FSP management ports.

Fix this in Power System E1080 \(9080 Hex\) Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45656 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45656 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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