dbcve.org
Tuning ManagerApplication · Hitachi

CVE-2020-36611

HIGH · 7.1 CVSS v3.1 Published 2023-01-17
Fix available
A fix is available. Upgrade to 8.8.5-00 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 Tuning Manager on Linux (Hitachi Tuning Manager server, Hitachi Tuning Manager - Agent for RAID, Hitachi Tuning Manager - Agent for NAS, Hitachi Tuning Manager - Agent for SAN Switch components) allows local users to read and write specific files.This issue affects Hitachi Tuning Manager: before 8.8.5-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 · moderate confidence

Incorrect default file permissions in Hitachi Tuning Manager on Linux (versions before 8.8.5-00) allow local unprivileged users to read and write specific configuration or data files that should be restricted. This affects the server component and multiple agent components (RAID, NAS, SAN Switch).

MitigationApply vendor patch to upgrade to Hitachi Tuning Manager version 8.8.5-00 or later which corrects the default file permissions. If immediate patching is not feasible, identify and harden the affected files with restrictive permissions (e.g., 640 or 600) owned by the application service account.

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
Tuning ManagerApplication
Affected:< 8.8.5-00

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. Check installed Hitachi Tuning Manager version
    Run 'rpm -qa | grep -i hitachi' or 'ls -la /opt' to locate the installation directory, then check the version file or run the version command for the product
    Affected if The installed version is lower than 8.8.5-00
  2. Locate server component configuration files
    Find the main installation directory (commonly under /opt/Hitachi or similar), then look for conf, config, or data subdirectories in the server component
    Affected if Server component configuration files exist and are readable by unprivileged users
  3. Check permissions on server configuration files
    Run 'ls -la' on configuration directories and files in the server component. Look for files with permissions like 644, 666, or world-writable (o+w)
    Affected if Configuration files have permissions allowing read or write access by other users (o+r or o+w)
  4. Locate agent component directories (RAID, NAS, SAN Switch)
    Under the main installation directory, locate subdirectories for agent components (often named like raid, nas, sanr, etc.)
    Affected if Agent component directories and their configuration files exist
  5. Check permissions on agent configuration and data files
    Run 'ls -la' on agent directories and their conf/config/data files
    Affected if Agent configuration or data files are readable or writable by unprivileged users (permissions include o+r or o+w)

The system is affected if Hitachi Tuning Manager version is below 8.8.5-00 AND configuration/data files in the server or agent components have overly permissive permissions (world-readable or world-writable), allowing unprivileged local users to access sensitive 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
Upgrade available Upgrade to 8.8.5-00 or later
Fixed in 8.8.5-00
Interim mitigation

Apply vendor patch to upgrade to Hitachi Tuning Manager version 8.8.5-00 or later which corrects the default file permissions. If immediate patching is not feasible, identify and harden the affected files with restrictive permissions (e.g., 640 or 600) owned by the application service account.

Recommended fix Moderate confidence

8.8.5-00

  1. 1. Back up all Tuning Manager configuration files, databases, and important data
  2. 2. Download Hitachi Tuning Manager version 8.8.5-00 or later from the official Hitachi support portal
  3. 3. Stop all Tuning Manager services using the appropriate service management commands (e.g., systemctl stop or service commands)
  4. 4. Install the upgraded Tuning Manager version 8.8.5-00 following the official installation guide
  5. 5. After installation, verify that file permissions are correctly set on affected files and directories
  6. 6. Start the Tuning Manager services
  7. 7. Verify the installation was successful and the service is running properly
Caveat Review release notes for any configuration changes or compatibility considerations before upgrading

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

Fix this in Tuning Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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