CVE-2020-36652
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 Automation Director on Linux, Hitachi Infrastructure Analytics Advisor on Linux (Hitachi Infrastructure Analytics Advisor, Analytics probe server components), Hitachi Ops Center Automator on Linux, Hitachi Ops Center Analyzer on Linux (Hitachi Ops Center Analyzer, Analyzer probe server components), Hitachi Ops Center Viewpoint on Linux (Viewpoint RAID Agent component) allows local users to read and write specific files. This issue affects Hitachi Automation Director: from 8.2.0-00 through 10.6.1-00; Hitachi Infrastructure Analytics Advisor: from 2.0.0-00 through 4.0.0-00; Hitachi Ops Center Automator: before 10.9.1-00; Hitachi Ops Center Analyzer: before 10.9.1-00; Hitachi Ops Center Viewpoint: before 10.9.1-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 confidenceMultiple Hitachi enterprise products on Linux ship with incorrect default file permissions, allowing local unprivileged users to read and write sensitive configuration or data files that should be restricted. This represents a privilege boundary violation where the application defaults to overly permissive file access controls.
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.2.0-00, <= 10.6.1-00>= 2.0.0-00, <= 4.0.0-00< 10.9.1-00< 10.9.1-00< 10.9.1-00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hitachi productsRun 'rpm -qa | grep -i hitachi' or 'dpkg -l | grep -i hitachi' to list installed Hitachi packages on the Linux systemAffected if Any of these products are installed: Automation Director, Infrastructure Analytics Advisor, Ops Center Analyzer, Ops Center Automator, or Ops Center Viewpoint
-
Determine product versionFor each detected Hitachi product, query its version using 'rpm -qi <package-name>' or 'dpkg -s <package-name>', or check /opt/hitachi directory for version filesAffected if Version falls within: Automation Director 8.2.0-00 through 10.6.1-00, Infrastructure Analytics Advisor 2.0.0-00 through 4.0.0-00, or any Ops Center product (Analyzer, Automator, Viewpoint) below 10.9.1-00
-
Locate configuration and data directoriesSearch for Hitachi product directories under /opt/hitachi, /var/opt/hitachi, or the product-specific installation path found in step 1. Look for conf, config, data, or similar directories containing sensitive filesAffected if Configuration or data directories exist under the product installation path
-
Inspect file permissions on sensitive filesRun 'ls -la' on configuration directories (e.g., /opt/hitachi/*/conf) and check if files are world-readable (644 or lower with 'r--r--r--' permissions) or world-writable (622 or similar). Use 'find /path/to/config -perm -002' to find any world-writable filesAffected if Any configuration or sensitive data files show world-readable (o+r) or world-writable (o+w) permissions, indicating overly permissive access controls
-
Verify non-privileged user accessAs a non-root user, attempt to read or write to suspected configuration files identified in step 3 using 'cat' or 'echo' commandsAffected if A local unprivileged user can successfully read sensitive configuration files or modify data files that should be restricted
If any Hitachi product from the list is installed with a version in the affected range AND configuration/data files have world-readable or world-writable permissions, the environment is vulnerable to CVE-2020-36652.
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.
From vendor data10.9.1-00
Apply vendor-supplied patches (Hitachi Automation Director 10.7.0-00 or later, Infrastructure Analytics Advisor 4.1.0-00 or later, Ops Center products 10.9.1-00 or later) to remediate improper default file permissions. Until patched, restrict local physical and console access to systems running affected software.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36652 — 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-36652 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