dbcve.org
Hardware Management ConsoleApplication · Ibm

CVE-2025-1951

MEDIUM · 6.7 CVSS v3.1 Published 2025-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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 Hardware Management Console - Power Systems V10.2.1030.0 and V10.3.1050.0 could allow a local user to execute commands as a privileged user due to execution of commands with unnecessary privileges.

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 Hardware Management Console for Power Systems versions V10.2.1030.0 and V10.3.1050.0 contains a local privilege escalation vulnerability where an authenticated local user can execute commands as a privileged (root) user due to the software executing certain commands with unnecessary elevated privileges.

MitigationApply IBM's vendor-supplied updates to upgrade HMC to patched versions. Restrict local user access and monitor for unauthorized privilege escalation attempts until the patch is applied.

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
Hardware Management ConsoleApplication
Affected:= 10.2.1030.0= 10.3.1050.0

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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. Verify IBM HMC is installed
    Run 'lsrsrc IBM.MCP' or check for /opt/hmc directory existence on the system
    Affected if IBM Hardware Management Console software is present on the system
  2. Determine HMC version
    Execute 'lsrep -s' or check /etc/hmc_version file to retrieve the installed HMC version number
    Affected if Installed version matches exactly 10.2.1030.0 or 10.3.1050.0
  3. Identify local user accounts
    Run 'lsuser -R FILES -a id home shell ALL' or check /etc/passwd for local user accounts configured on the HMC
    Affected if Local user accounts exist on the HMC system
  4. Audit for unexpected privileged commands
    Review system logs in /var/log for commands executed by non-root users running under elevated (uid 0) process context
    Affected if Logs show non-root users executing commands with root privileges

The environment is affected if IBM Hardware Management Console is installed and the installed version is exactly 10.2.1030.0 or 10.3.1050.0 with local user accounts configured.

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

Apply IBM's vendor-supplied updates to upgrade HMC to patched versions. Restrict local user access and monitor for unauthorized privilege escalation attempts until the patch is applied.

Fix this in Hardware Management Console Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

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