CVE-2020-36695 json
File and Directory Permission Vulnerability in Hitachi Command Suite
published 2023-07-18 3 y ago modified 2026-06-17 4 mo ago also EUVD-2020-24137
- cvss
- 6.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
Incorrect 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.
Patch / fix
- Hitachi Hitachi Device Manager 8.8.5-02
- Hitachi Hitachi Tiered Storage Manager 8.8.5-02
- Hitachi Hitachi Replication Manager 8.8.5-02
- Hitachi Hitachi Tuning Manager 8.8.5-02
- Hitachi Hitachi Compute Systems Manager 8.8.3-08
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.6 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Hitachi Hitachi Device Manager
- Hitachi Hitachi Tiered Storage Manager
- Hitachi Hitachi Replication Manager
- Hitachi Hitachi Tuning Manager
- Hitachi Hitachi Compute Systems Manager
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
Sources
- CVE List CVE-2020-36695
- NVD CVE-2020-36695
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.