CVE-2025-2902
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 · uneditedImproper Authorization Vulnerability of Maintenance Utility in Hitachi Virtual Storage Platform. This issue affects Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H: before DKCMAIN Ver. 93-07-26-xx/00, GUM Ver. 93-07-26/00; Hitachi Virtual Storage Platform 5100, 5500, 5100H, 5500H, 5200, 5600, 5200H, 5600H: before DKCMAIN Ver. 90-09-27-00/00, GUM Ver. 90-09-27/00; Hitachi Virtual Storage Platform G130, G150, G350, G370, G700, G900, F350, F370, F700, F900: before DKCMAIN Ver. 88-08-16-xx/00, GUM Ver. 88-08-20/00.
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 confidenceThis is an improper authorization vulnerability in the maintenance utility component of Hitachi Virtual Storage Platform systems. The flaw allows unauthorized access to maintenance functions due to insufficient authorization controls, potentially enabling authenticated attackers to execute privileged maintenance operations. Affected systems span multiple VSP model families (E-series, 5000-series, and G/F-series) running DKCMAIN and GUM versions below the specified security patch levels.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your VSP model familyLocate the model label on the storage system chassis or check the system documentation/model number. Common families include E-series, 5000-series, and G/F-series.Affected if The model is an E-series, 5000-series, or G/F-series Hitachi VSP system
-
Determine the installed DKCMAIN firmware versionAccess the storage system management interface (such as Device Manager or the main console). Navigate to the firmware or system information section to locate the DKCMAIN version number.Affected if The DKCMAIN version is below 93-07-26-xx/00 (for E-series), 90-09-27-00/00 (for 5000-series), or 88-08-16-xx/00 (for G/F-series)
-
Determine the installed GUM firmware versionIn the same management interface, locate the GUM (Global Unified Management) version information, typically found under system firmware or controller firmware details.Affected if The GUM version is below 93-07-26-xx/00 (for E-series), 90-09-27-00/00 (for 5000-series), or 88-08-16-xx/00 (for G/F-series)
-
Verify the maintenance utility is accessibleCheck if the maintenance utility or maintenance mode interface is enabled and reachable on the system. This is typically accessible through the service port or special management interface used for maintenance operations.Affected if The maintenance utility component is enabled and accessible to authenticated users without additional authorization controls
You are affected if your VSP system runs a DKCMAIN or GUM version below the security patch levels for your model family and the maintenance utility is accessible to authenticated users.
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.
dbcve · scopedApply the vendor-provided DKCMAIN and GUM firmware updates to reach the security patch levels (93-07-26-xx/00, 90-09-27-00/00, or 88-08-16-xx/00 depending on model family). Schedule maintenance windows during planned outages and verify authorization controls post-update.
DKCMAIN Ver. 93-07-26-xx/00+ (E-series), 90-09-27-00/00+ (5x00 series), 88-08-16-xx/00+ (G/F series); with matching GUM versions
- 1. Identify the specific Hitachi Virtual Storage Platform model in your environment using the management interface or hardware labels
- 2. Determine the current DKCMAIN and GUM firmware versions by accessing the storage system's maintenance console or admin GUI
- 3. Consult Hitachi's official support portal (www.hitachi.com) or contact Hitachi support to obtain the correct firmware packages for your model
- 4. For E390/E590/E790/E990/E1090/E390H/E590H/E790H/E1090H systems: upgrade to DKCMAIN Ver. 93-07-26-xx/00 or later and GUM Ver. 93-07-26/00 or later
- 5. For 5100/5500/5100H/5500H/5200/5600/5200H/5600H systems: upgrade to DKCMAIN Ver. 90-09-27-00/00 or later and GUM Ver. 90-09-27/00 or later
- 6. For G130/G150/G350/G370/G700/G900/F350/F370/F700/F900 systems: upgrade to DKCMAIN Ver. 88-08-16-xx/00 or later and GUM Ver. 88-08-20/00 or later
- 7. Schedule a maintenance window as storage array upgrades typically require system downtime
- 8. Follow Hitachi's documented firmware installation procedure for your specific model, which typically involves uploading the firmware via the maintenance utility and initiating the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2902 — 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-2025-2902 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