CVE-2024-45094
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 DS8900F and DS8A00 Hardware Management Console (HMC) is vulnerable to stored cross-site scripting. This vulnerability allows a privileged user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
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 · moderate confidenceStored XSS vulnerability in IBM DS8900F and DS8A00 Hardware Management Console allows privileged users to inject malicious JavaScript into the Web UI. This injected code executes in the browsers of other users viewing the affected interface, potentially exfiltrating session credentials or performing actions on behalf of trusted users.
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= 10.0.245.0= 10.1.3.0= 89.40.83.0= 89.41.25.0= 89.42.18.0= 89.33.45.0= 89.33.52.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 the HMC firmware versionAccess the Hardware Management Console via SSH or console and run the command to display the firmware version (typically 'lshmc -v' or check the HMC web interface system information page)Affected if The installed firmware version matches one of the affected versions: 10.0.245.0, 10.1.3.0, 89.40.83.0, 89.41.25.0, 89.42.18.0, 89.33.45.0, or 89.33.52.0
-
Confirm the Web UI is enabledLog into the HMC and verify that the web-based management interface (HMC Web UI) is accessible and enabled. Check via the HMC management interface or by attempting to reach the web console URLAffected if The Web UI is enabled and accessible to users on the network
-
Verify privileged user access existsCheck if there are any privileged user accounts configured on the HMC that could potentially inject content into the Web UI interface. Review user accounts via 'hmcuser' or similar management commandsAffected if Privileged user accounts exist with the ability to interact with the Web UI input fields where XSS could be injected
-
Check for recent security patchesReview the HMC firmware change log or patch history to determine if IBM's security patch for CVE-2024-45094 has been appliedAffected if The installed firmware version is one of the affected versions AND no corresponding security patch has been applied
You are affected if your HMC firmware version matches any of the listed affected versions AND the Web UI is enabled, as this combination allows the stored XSS vulnerability to be exploited.
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 IBM's security patch for this vulnerability. Until patched, implement Content Security Policy (CSP) headers and input validation/sanitization on the HMC web interface to block XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45094 — 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-45094 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