dbcve.org
Ds8a00 FirmwareOperating system · Ibm

CVE-2025-36192

HIGH · 7.1 CVSS v3.1 Published 2025-12-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 DS8A00( R10.1) 10.10.106.0 and IBM DS8A00 ( R10.0) 10.1.3.010.2.45.0 and IBM DS8900F ( R9.4) 89.40.83.089.42.18.089.44.5.0 IBM System Storage DS8000 could allow a local user with authorized CCW update permissions to delete or corrupt backups due to missing authorization in IBM Safeguarded Copy / GDPS Logical corruption protection mechanisms.

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 DS8000 storage systems contain a missing authorization vulnerability in Safeguarded Copy and GDPS Logical corruption protection mechanisms. A local user with authorized CCW (Channel Command Word) update permissions can exploit this to delete or corrupt backups, bypassing the intended access controls on backup protection features.

MitigationApply IBM-provided patches for the affected DS8000 firmware versions (R10.1, R10.0, R9.4). Review and restrict CCW update permissions to only essential personnel until patches are 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
Ds8a00 FirmwareOperating system
Affected:= 10.10.106.0= 10.1.3.0= 10.2.45.0= 89.40.83.0= 89.42.18.0= 89.44.5.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 DS8000 firmware version
    Access the DS8000 management interface (DS GUI or CLI) and retrieve the current firmware version. This is typically found in the system overview or hardware status section. Use the command 'lsfmsys' or check via the DS8000增殖管理 GUI under System > Hardware > Microcode Levels.
    Affected if The installed firmware version matches exactly one of: 10.10.106.0, 10.1.3.0, 10.2.45.0, 89.40.83.0, 89.42.18.0, or 89.44.5.0
  2. Verify user CCW update permissions
    Review user access permissions in the DS8000 management interface. Navigate to Security > User Management or use the 'lsusr' command to list users and their assigned roles. Check specifically for CCW (Channel Command Word) update privileges assigned to any local users.
    Affected if Any local user account is granted CCW update permissions (typically listed as 'CCW Update' or 'Channel Command Word Update' in the user's role/permissions)
  3. Confirm Safeguarded Copy feature status
    Check if Safeguarded Copy is configured on the DS8000. Use the 'lscopy' or 'lsguardedcopy' command in the DS CLI, or navigate to Data Protection > Safeguarded Copy in the DS GUI to view active copy relationships.
    Affected if Safeguarded Copy is enabled and there are active protected copy relationships configured on the storage system
  4. Confirm GDPS Logical corruption protection status
    Verify if GDPS (Geographic Disk Pool System) Logical Corruption protection is active. Use the 'lsgdps' command or check through the DS GUI under Data Protection > GDPS configurations. Look for any Logical Corruption protection domain configurations.
    Affected if GDPS Logical Corruption protection is configured and active on the DS8000 system

A user is affected if the DS8000 runs one of the listed firmware versions AND has a user with CCW update permissions AND Safeguarded Copy or GDPS Logical Corruption protection features are actively configured on the system.

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-provided patches for the affected DS8000 firmware versions (R10.1, R10.0, R9.4). Review and restrict CCW update permissions to only essential personnel until patches are applied.

Fix this in Ds8a00 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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