dbcve.org
Power System Ac922 \(8335 Gtg\) FirmwareOperating system · Ibm

CVE-2021-38961

MEDIUM · 6.1 CVSS v3.1 Published 2021-12-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 OPENBMC OP910 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 212049.

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 confidence

IBM OpenBMC OP910 contains a cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed arbitrary JavaScript code through the web interface, potentially altering application functionality and enabling credential disclosure within trusted user sessions.

MitigationRemediate by implementing proper input validation and output encoding/sanitization for all user-supplied data in the Web UI, followed by a firmware update to the latest patched version.

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 Ac922 \(8335 Gtg\) FirmwareOperating system
Affected:= op910
Power System Ac922 \(8335 Gtc\) FirmwareOperating system
Affected:= op910
Power System Ac922 \(8335 Gtw\) FirmwareOperating system
Affected:= op910

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Identify the hardware model
    Query the BMC for the system model using IPMI or Redfish API: `ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> chassis status` or via Redfish GET /Systems/1
    Affected if The system is not an IBM Power System Ac922 model 8335 (GTG, GTC, or GTW)
  2. Check the BMC firmware version
    Retrieve the BMC firmware version via IPMI: `ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> mc info` or via Redfish GET /Managers/1/FirmwareInventory
    Affected if The firmware version equals op910 exactly (this specific version is vulnerable)
  3. Confirm the Web UI is enabled
    Check if the OpenBMC web interface is listening and accessible: `curl -k https://<bmc_ip>` or verify port 443/8443 is open
    Affected if The Web UI is disabled or not accessible - the XSS requires the web interface to be reachable

You are affected if you have an IBM Power System Ac922 (8335 GTG/GTC/GTW) running firmware version op910 with the OpenBMC Web UI enabled.

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

Remediate by implementing proper input validation and output encoding/sanitization for all user-supplied data in the Web UI, followed by a firmware update to the latest patched version.

Fix this in Power System Ac922 \(8335 Gtg\) Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-38961 — 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-2021-38961 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