CVE-2020-36695
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 · uneditedIncorrect Default Permissions vulnerability in Hitachi Device Manager on Linux (Device Manager Server component), Hitachi Tiered Storage Manager on Linux, Hitachi Replication Manager on Linux, Hitachi Tuning Manager on Linux (Hitachi Tuning Manager server, Hitachi Tuning Manager - Agent for RAID, Hitachi Tuning Manager - Agent for NAS components), Hitachi Compute Systems Manager on Linux allows File Manipulation.This issue affects Hitachi Device Manager: before 8.8.5-02; Hitachi Tiered Storage Manager: before 8.8.5-02; Hitachi Replication Manager: before 8.8.5-02; Hitachi Tuning Manager: before 8.8.5-02; Hitachi Compute Systems Manager: before 8.8.3-08.
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 confidenceIncorrect default file permissions in multiple Hitachi management products (Device Manager, Tiered Storage Manager, Replication Manager, Tuning Manager, Compute Systems Manager) on Linux allow unauthorized file manipulation. Files created during installation or operation have overly permissive access controls, potentially enabling low-privilege local users to modify or overwrite critical configuration or data files.
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< 8.8.3-08< 8.8.5-02< 8.8.5-02< 8.8.5-02< 8.8.5-02CVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hitachi management productsRun 'rpm -qa | grep -i hitachi' or 'dpkg -l | grep -i hitachi' to list installed Hitachi packages on the Linux systemAffected if Any of the following products are present: Compute Systems Manager, Device Manager, Replication Manager, Tiered Storage Manager, or Tuning Manager
-
Determine installed version of each productFor each installed Hitachi product, run 'rpm -qi <package-name>' or 'dpkg -s <package-name>' to retrieve the version numberAffected if The installed version is lower than 8.8.3-08 for Compute Systems Manager, or lower than 8.8.5-02 for Device Manager, Replication Manager, Tiered Storage Manager, or Tuning Manager
-
Locate product installation directoriesRun 'find /opt -maxdepth 2 -type d -iname "*hitachi*" -o -iname "*hcs*" -o -iname "*hnos*" 2>/dev/null' to find Hitachi installation directories, then inspect file permissions within those directoriesAffected if Installation directories or key configuration/data files are found with overly permissive permissions (such as world-writable or group-writable settings)
-
Check for world-writable files in product directoriesIn each identified Hitachi product installation directory, run 'find <directory> -type f -perm -002' to locate files with world-writable permissionsAffected if Any configuration, script, or data files under the product installation paths have world-writable permissions that could allow low-privilege users to modify critical files
A system is affected if any Hitachi management product listed above is installed at a version lower than the fixed releases, AND the installation directories contain files with overly permissive (world-writable) permissions.
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 · scoped8.8.3-088.8.5-02
Upgrade all affected Hitachi products to the specified versions (Device Manager, Tiered Storage Manager, Replication Manager, Tuning Manager to 8.8.5-02; Compute Systems Manager to 8.3.3-08) which contain corrected default file permissions.
Compute Systems Manager: 8.8.3-08 | Device Manager: 8.8.5-02 | Replication Manager: 8.8.5-02 | Tiered Storage Manager: 8.8.5-02 | Tuning Manager: 8.8.5-02
- Identify which Hitachi products from the affected list are installed: Compute Systems Manager, Device Manager, Replication Manager, Tiered Storage Manager, or Tuning Manager
- Check the current installed version of each product
- For Compute Systems Manager: upgrade to version 8.8.3-08 or later
- For Device Manager: upgrade to version 8.8.5-02 or later
- For Replication Manager: upgrade to version 8.8.5-02 or later
- For Tiered Storage Manager: upgrade to version 8.8.5-02 or later
- For Tuning Manager: upgrade to version 8.8.5-02 or later
- After upgrade, verify file permissions on installation directories are correctly set with restrictive access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36695 — 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-2020-36695 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