Storage Plug InApplication · Hitachi

CVE-2024-21840

HIGH · 7.1 CVSS v3.1 Published 2024-01-30
Fix available
A fix is available. Upgrade to 04.10.0 or later.
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
Incorrect Default Permissions vulnerability in Hitachi Storage Plug-in for VMware vCenter allows local users to read and write specific files. This issue affects Hitachi Storage Plug-in for VMware vCenter: from 04.0.0 through 04.9.2.

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

The Hitachi Storage Plug-in for VMware vCenter versions 04.0.0 through 04.9.2 ships with overly permissive default file permissions on specific files. Local users with standard account access can read and write to these files, potentially allowing privilege escalation or access to sensitive configuration/data.

MitigationUpdate to version 04.9.3 or later which corrects the default file permissions, or manually review and restrict permissions on affected files according to vendor guidance.

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
Storage Plug InApplication
Affected:>= 04.0.0, < 04.10.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
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 Hitachi Storage Plug-in for VMware vCenter is installed
    Locate the plugin installation directory on the vCenter server. Common paths include /opt/vmware/vcops/vcopsIntegration/ or C:\Program Files\VMware\vCenter Server\extensions\ on Windows. Check for directories containing 'Hitachi' or 'HDS' in the name.
    Affected if The plugin is present on the system
  2. Determine the installed plugin version
    Check the plugin version by reviewing version files in the installation directory, or run the plugin's version command if available (for example, examine the manifest.xml or version.info file within the plugin directory).
    Affected if The version is 04.0.0 through 04.9.2 (any version < 04.10.0)
  3. Inspect file permissions on plugin files
    Use 'ls -la' (Linux) or icacls (Windows) to list permissions on the plugin installation directory and its contents. Look for files with permissions allowing read or write access to standard (non-admin) users or 'Everyone' group.
    Affected if Files grant read or write access to standard user accounts or overly broad groups

The environment is affected if the Hitachi Storage Plug-in for VMware vCenter is installed with a version between 04.0.0 and 04.9.2 and has files with overly permissive access controls.

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
Upgrade available Upgrade to 04.10.0 or later
Fixed in 04.10.0
Interim mitigation

Update to version 04.9.3 or later which corrects the default file permissions, or manually review and restrict permissions on affected files according to vendor guidance.

Recommended fix High confidence

04.10.0 or later

  1. 1. Identify the current version of Hitachi Storage Plug-in for VMware vCenter installed in your environment
  2. 2. Download Hitachi Storage Plug-in for VMware vCenter version 04.10.0 or later from the official Hitachi support portal
  3. 3. Follow Hitachi's official upgrade documentation to apply the update to your VMware vCenter environment
  4. 4. After upgrading, verify that the default file permissions have been corrected and are no longer world-readable/writable

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

Fix this in Storage Plug In Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21840 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21840 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