dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2022-36407

CRITICAL · 9.9 CVSS v3.1 Published 2024-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual Storage Platform VP9500, Hitachi Virtual Storage Platform G1000, G1500, Hitachi Virtual Storage Platform F1500, Hitachi Virtual Storage Platform 5100, 5500, 5100H, 5500H, Hitachi Virtual Storage Platform 5200, 5600, 5200H, 5600H, Hitachi Unified Storage VM, Hitachi Virtual Storage Platform G100, G200, G400, G600, G800, Hitachi Virtual Storage Platform F400, F600, F800, Hitachi Virtual Storage Platform G130, G150, G350, G370, G700, G900, Hitachi Virtual Storage Platform F350, F370, F700, F900, Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H allows local users to gain sensitive information.This issue affects Hitachi Virtual Storage Platform: before DKCMAIN Ver. 70-06-74-00/00, SVP Ver. 70-06-58/00; Hitachi Virtual Storage Platform VP9500: before DKCMAIN Ver. 70-06-74-00/00, SVP Ver. 70-06-58/00; Hitachi Virtual Storage Platform G1000, G1500: before DKCMAIN Ver. 80-06-92-00/00, SVP Ver. 80-06-87/00; Hitachi Virtual Storage Platform F1500: before DKCMAIN Ver. 80-06-92-00/00, SVP Ver. 80-06-87/00; Hitachi Virtual Storage Platform 5100, 5500,5100H, 5500H: before DKCMAIN Ver. 90-08-81-00/00, SVP Ver. 90-08-81/00, before DKCMAIN Ver. 90-08-62-00/00, SVP Ver. 90-08-62/00, before DKCMAIN Ver. 90-08-43-00/00, SVP Ver. 90-08-43/00; Hitachi Virtual Storage Platform 5200, 5600,5200H, 5600H: before DKCMAIN Ver. 90-08-81-00/00, SVP Ver. 90-08-81/00, before DKCMAIN Ver. 90-08-62-00/00, SVP Ver. 90-08-62/00, before DKCMAIN Ver. 90-08-43-00/00, SVP Ver. 90-08-43/00; Hitachi Unified Storage VM: before DKCMAIN Ver. 73-03-75-X0/00, SVP Ver. 73-03-74/00, before DKCMAIN Ver. 73(75)-03-75-X0/00, SVP Ver. 73(75)-03-74/00; Hitachi Virtual Storage Platform G100, G200, G400, G600, G800: before DKCMAIN Ver. 83-06-19-X0/00, SVP Ver. 83-06-20-X0/00, before DKCMAIN Ver. 83-05-47-X0/00, SVP Ver. 83-05-51-X0/00; Hitachi Virtual Storage Platform F400, F600, F800: before DKCMAIN Ver. 83-06-19-X0/00, SVP Ver. 83-06-20-X0/00, before DKCMAIN Ver. 83-05-47-X0/00, SVP Ver. 83-05-51-X0/00; Hitachi Virtual Storage Platform G130, G150, G350, G370, G700, G900: before DKCMAIN Ver. 88-08-09-XX/00, SVP Ver. 88-08-11-X0/02; Hitachi Virtual Storage Platform F350, F370, F700, F900: before DKCMAIN Ver. 88-08-09-XX/00, SVP Ver. 88-08-11-X0/02; Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H: before DKCMAIN Ver. 93-06-81-X0/00, SVP Ver. 93-06-81-X0/00, before DKCMAIN Ver. 93-06-62-X0/00, SVP Ver. 93-06-62-X0/00, before DKCMAIN Ver. 93-06-43-X0/00, SVP Ver. 93-06-43-X0/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 confidence

Hitachi Virtual Storage Platform products contain a vulnerability where sensitive information (such as credentials, tokens, or configuration data) is being written to log files. Local users with access to these log files can obtain this sensitive information, leading to potential credential theft or further system compromise. The vulnerability affects numerous VSP model families across different firmware versions (DKCMAIN and SVP).

MitigationApply the appropriate firmware updates (DKCMAIN and SVP versions) as specified in the advisory for each affected product family. Prioritize systems based on local user access exposure and verify that sensitive data is not persisted in log files after the update.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify VSP model and firmware type
    Determine if your Hitachi VSP system uses DKCMAIN firmware (storage controller) or SVP (Service Processor). Check your system documentation or use vendor-provided tools to query the model family and firmware type.
    Affected if System is a Hitachi VSP model using DKCMAIN or SVP firmware
  2. Check installed firmware version
    Use Hitachi command-line tools or management interface to query the current firmware version. Compare against known affected version ranges for your specific model family.
    Affected if Installed firmware version falls within an affected version range for your VSP model family
  3. Locate and inspect log files
    Access the system log directory (typically found in system management paths or via Hitachi utilities). Search log files for patterns indicating sensitive data: passwords, tokens, API keys, user credentials, or configuration containing authentication information.
    Affected if Log files contain readable sensitive information such as credentials, tokens, or authentication configuration data
  4. Check log file access controls
    Review file permissions on log directories and files. Determine if local users other than administrators can read log files.
    Affected if Log files are readable by non-privileged local users and contain sensitive data
  5. Verify model family in affected list
    Confirm your specific VSP model family (e.g., VSP 5000 series, VSP E series, etc.) is among the families listed as affected by CVE-2022-36407.
    Affected if Your specific VSP model family and firmware version combination is documented as vulnerable

A system is affected if it is a Hitachi VSP product running vulnerable DKCMAIN or SVP firmware AND has log files accessible to local users that contain sensitive information such as credentials, tokens, or authentication data.

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 appropriate firmware updates (DKCMAIN and SVP versions) as specified in the advisory for each affected product family. Prioritize systems based on local user access exposure and verify that sensitive data is not persisted in log files after the update.

Recommended fix High confidence

Upgrade to DKCMAIN and SVP versions at or after the fixed releases: 70-06-74-00/00/70-06-58 for VSP, 80-06-92-00/00/80-06-87 for G1000/G1500/F1500, 90-08-81-00/00/90-08-81 for 5100/5500/5200/5600 series, 73-03-75-X0/00/73-03-74 for Unified Storage VM, 83-06-19-X0/00/83-06-20-X0/00 for G100-G800/F400

  1. Identify the specific Hitachi Virtual Storage Platform model in use by checking the system configuration or SVP management interface
  2. Determine the current DKCMAIN and SVP firmware versions installed on the system
  3. Consult the Hitachi product documentation or support portal to obtain the correct firmware version for the specific model
  4. Download the fixed firmware version (DKCMAIN Ver. 70-06-74-00/00 or later for VSP, DKCMAIN Ver. 80-06-92-00/00 or later for G1000/G1500/F1500, DKCMAIN Ver. 90-08-81-00/00 or later for 5100/5500/5200/5600 series, DKCMAIN Ver. 73-03-75-X0/00 or later for Unified Storage VM, DKCMAIN Ver. 83-06-19-X0/00 or later for G100-G800/F400-F800, DKCMAIN Ver. 88-08-09-XX/00 or later for G130-G900/F350-F900, DKC
  5. Schedule a maintenance window following Hitachi's recommended upgrade procedure
  6. Apply the firmware upgrade following Hitachi's official upgrade documentation, ensuring both DKCMAIN and SVP components are updated
  7. After upgrade, verify the new versions are installed correctly
  8. Review system logs to confirm the vulnerability is remediated
Caveat Follow Hitachi's standard firmware upgrade procedures; ensure proper backup and test in non-production environment first as with any storage array firmware update

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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