CVE-2019-17360
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 · uneditedA vulnerability in Hitachi Command Suite 7.x and 8.x before 8.7.0-00 allows an unauthenticated remote user to trigger a denial of service (DoS) condition because of Uncontrolled Resource Consumption.
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 confidenceHitachi Command Suite versions 7.x and 8.x before 8.7.0-00 contain an uncontrolled resource consumption vulnerability that allows unauthenticated remote attackers to trigger denial of service conditions. The vulnerability is exploitable remotely without authentication, likely through malformed or repetitive requests that exhaust memory, CPU, file handles, or network connections.
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>= 7.0.0-00, < 8.7.0-00>= 7.0.0-00, < 8.7.0-00>= 7.0.0-00, < 8.7.0-00>= 2.0.0-00, < 10.0.0-01>= 6.0.0-00, < 10.0.0-00>= 7.0.0-00, < 8.7.0-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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Command Suite componentsCheck the programs and features list on the Windows server, or look for Hitachi installation directories under Program Files or /opt. Common component names include Device Manager, Replication Manager, Tiered Storage Manager, Infrastructure Analytics Advisor, and Tuning Manager.Affected if Any of these components are installed but the version cannot be determined or is below 8.7.0-00 (or 10.0.0-01/10.0.0-00 for Infrastructure Analytics Advisor)
-
Check the version of Hitachi Device ManagerOpen the Hitachi Device Manager management console, or check the version information in the installation directory. The version is typically displayed in the About or Help section of the web interface or desktop client.Affected if Installed version is 7.x.x-00 through 8.x.x (but less than 8.7.0-00)
-
Check the version of Hitachi Replication ManagerOpen the Hitachi Replication Manager management interface and navigate to the About or Version section, or inspect version files in the installation directory.Affected if Installed version is 7.x.x-00 through 8.x.x (but less than 8.7.0-00)
-
Check the version of Hitachi Tiered Storage ManagerAccess the Tiered Storage Manager console or check version files in the installation directory, typically found under the Hitachi product directory.Affected if Installed version is 7.x.x-00 through 8.x.x (but less than 8.7.0-00)
-
Check the version of Hitachi Infrastructure Analytics AdvisorOpen the Infrastructure Analytics Advisor web interface or desktop client and locate the version information in the About or System Information section.Affected if Installed version is >= 2.0.0-00 and < 10.0.0-01, OR >= 6.0.0-00 and < 10.0.0-00
-
Check the version of Hitachi Tuning ManagerAccess the Tuning Manager interface and look for version information in the About or Help menu, or check version files in the installation directory.Affected if Installed version is 7.x.x-00 through 8.x.x (but less than 8.7.0-00)
A system is affected if any Hitachi Command Suite component (Device Manager, Replication Manager, Tiered Storage Manager, Infrastructure Analytics Advisor, or Tuning Manager) is installed at version 7.x.x-00 through 8.x.x (but below 8.7.0-00 for most components, or below 10.0.0-01/10.0.0-00 for Infrastructure Analytics Advisor), especially if the management interface is exposed to untrusted networ
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 data8.7.0-0010.0.0-0010.0.0-01
Upgrade Hitachi Command Suite to version 8.7.0-00 or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation or firewall rules to limit exposure of the management interface to untrusted networks.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.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,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17360 — 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-2019-17360 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