dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-7737

HIGH · 8.6 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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
DoS Vulnerability in 10G iSCSI Interface of Hitachi Virtual Storage Platform. This issue affects Hitachi Virtual Storage Platform E990, E1090, E1090H: before DKCMAIN Ver.93-07-21-80/00-05, CHB(iSCSI) Ver.88-01-02-04, before DKCMAIN Ver.93-07-01-80/00-07, CHB(iSCSI) Ver.88-01-02-04, before DKCMAIN Ver.93-06-82-80/00-06, CHB(iSCSI) Ver.88-01-02-04, before DKCMAIN Ver.93-06-63-80/00-04, CHB(iSCSI) Ver.88-01-02-04; Hitachi Virtual Storage Platform E390, E590, E790, E390H, E590H, E790H: before DKCMAIN Ver.93-07-21-x0/00-05, CHB(iSCSI) Ver.88-01-02-04, before DKCMAIN Ver.93-07-01-x0/00-07, CHB(iSCSI) Ver.88-01-02-04, before DKCMAIN Ver.93-06-82-x0/00-06, CHB(iSCSI) Ver.88-01-02-04, before DKCMAIN Ver.93-06-63-x0/00-04, CHB(iSCSI) Ver.88-01-02-04, before DKCMAIN Ver.93-07-24-x0/00-02, CHB(iSCSI) Ver.88-01-02-04, before DKCMAIN Ver.93-07-02-x0/00-02, CHB(iSCSI) Ver.88-01-02-04; Hitachi Virtual Storage Platform G130, G150, G350, G370, G700, G900, F350, F370, F700, F900: before DKCMAIN Ver.88-08-10-x0/00-05, CHB(iSCSI) Ver.88-01-02-04; Hitachi Virtual Storage Platform G100, G200, G400, G600, G800, F400, F600, F800: before DKCMAIN Ver.83-06-20-x0/00-05, CHB(iSCSI) Ver.83-01-01-29; Hitachi Virtual Storage Platform VX8, 5100, 5500, 5100H, 5500H, 5200, 5600, 5200H, 5600H: before DKCMAIN Ver.90-09-01-00/01-01, CHB(iSCSI) Ver.90-01-01-07, before DKCMAIN Ver.90-08-83-00/01-01, CHB(iSCSI) Ver.90-01-01-07, before DKCMAIN Ver.90-08-63-00/01-01, CHB(iSCSI) Ver.90-01-01-07; Hitachi Virtual Storage Platform VX7, G1000, G1500, F1500: before DKCMAIN Ver.80-06-93-00/00-04, ISFC Ver.80-01-17.

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

A denial of service vulnerability exists in the 10G iSCSI interface (CHB iSCSI) of multiple Hitachi Virtual Storage Platform models. An attacker exploiting this vulnerability against the iSCSI target interface can cause the storage array to become unresponsive, disrupting host access to stored data.

MitigationApply the vendor-specified DKCMAIN and CHB(iSCSI) firmware version updates for each affected model. This requires scheduling a maintenance window and following Hitachi's documented firmware upgrade procedures for the VSP platform.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 storage array model
    Access the storage system management interface or use the Hitachi Command Suite/Storage Navigator to confirm the exact VSP model number (e.g., VSP 5100, 5300, 5500, 5600, 6100, 6200, 6500, 6600, E590, E790, E990).
    Affected if The model is one of the Hitachi Virtual Storage Platform models that supports CHB iSCSI interfaces.
  2. Verify CHB iSCSI interface is configured
    Check the storage array configuration through the management interface or CLI to determine if any 10G iSCSI CHB ports are provisioned and online. Look for CHB iSCSI target configurations or iSCSI qualified names (IQNs) registered on the system.
    Affected if CHB iSCSI interfaces are actively configured or enabled on the storage array.
  3. Locate firmware version information
    Access the storage system maintenance terminal or management GUI and navigate to the firmware/diagnostics section. Identify the current DKCMAIN firmware version and the CHB(iSCSI) firmware microcode version installed on the array.
    Affected if The installed firmware versions are older than the vendor-specified fixed versions for your specific model.
  4. Review iSCSI target exposure
    Examine network configuration to determine if the CHB iSCSI target ports are reachable from untrusted networks. Check firewall rules, zoning, and access control lists governing the iSCSI target interfaces.
    Affected if The iSCSI target interfaces are exposed to network segments accessible by potential attackers (not isolated within a secured management network).

A user is affected if they operate a Hitachi VSP model with CHB iSCSI interfaces configured and the installed DKCMAIN/CHB firmware versions have not been updated to the vendor-fixed releases.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-specified DKCMAIN and CHB(iSCSI) firmware version updates for each affected model. This requires scheduling a maintenance window and following Hitachi's documented firmware upgrade procedures for the VSP platform.

Recommended fix High confidence

DKCMAIN and CHB(iSCSI) firmware versions as specified per product model (see steps 4-9 for specific version targets)

  1. 1. Identify the specific Hitachi Virtual Storage Platform model in your environment from the affected list (E990, E1090, E1090H, E390, E590, E790, E390H, E590H, E790H, G130, G150, G350, G370, G700, G900, F350, F370, F700, F900, G100, G200, G400, G600, G800, F400, F600, F800, VX8, 5100, 5500, 5100H, 5500H, 5200, 5600, 5200H, 5600H, VX7, G1000, G1500, F1500).
  2. 2. Check the current DKCMAIN firmware version on the storage system using the appropriate management interface or command-line tool.
  3. 3. Check the current CHB(iSCSI) firmware version on the 10G iSCSI interface.
  4. 4. For E990, E1090, E1090H: Upgrade to DKCMAIN Ver.93-07-21-80/00-05 or later with CHB(iSCSI) Ver.88-01-02-04.
  5. 5. For E390, E590, E790, E390H, E590H, E790H: Upgrade to one of the fixed versions (DKCMAIN Ver.93-07-21-x0/00-05, Ver.93-07-01-x0/00-07, Ver.93-06-82-x0/00-06, Ver.93-06-63-x0/00-04, Ver.93-07-24-x0/00-02, or Ver.93-07-02-x0/00-02) with CHB(iSCSI) Ver.88-01-02-04.
  6. 6. For G130, G150, G350, G370, G700, G900, F350, F370, F700, F900: Upgrade to DKCMAIN Ver.88-08-10-x0/00-05 or later with CHB(iSCSI) Ver.88-01-02-04.
  7. 7. For G100, G200, G400, G600, G800, F400, F600, F800: Upgrade to DKCMAIN Ver.83-06-20-x0/00-05 or later with CHB(iSCSI) Ver.83-01-01-29.
  8. 8. For VX8, 5100, 5500, 5100H, 5500H, 5200, 5600, 5200H, 5600H: Upgrade to a fixed version (DKCMAIN Ver.90-09-01-00/01-01, Ver.90-08-83-00/01-01, or Ver.90-08-63-00/01-01) with CHB(iSCSI) Ver.90-01-01-07.
Caveat Firmware upgrades may require brief system downtime; ensure proper backup and maintenance window planning

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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