CVE-2017-8985
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 · uneditedHPE XP Storage using Hitachi Global Link Manager (HGLM) has a local authenticated information disclosure vulnerability in HGLM version HGLM 6.3.0-00 to 8.5.2-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 confidenceHPE XP Storage systems running Hitachi Global Link Manager (HGLM) versions 6.3.0-00 through 8.5.2-00 contain a local authenticated information disclosure vulnerability. An authenticated local attacker could potentially access sensitive information due to improper access controls within the HGLM component.
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>= 6.3.0-00, <= 8.5.2-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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm HPE XP Storage environmentIdentify if your storage infrastructure includes HPE XP Storage systems. Check your asset inventory or storage management console for HPE XP series storage arrays.Affected if You do not have HPE XP Storage systems in your environment.
-
Verify Hitachi Global Link Manager (HGLM) is installedCheck for the presence of Hitachi Global Link Manager software on your HPE XP Storage management server or client systems. This is typically listed in installed programs or running services.Affected if HGLM is not installed on your systems.
-
Determine HGLM versionAccess the HGLM management interface or use the software's version information function to identify the installed HGLM version number. Compare the version to the affected range 6.3.0-00 through 8.5.2-00.Affected if The installed HGLM version falls within 6.3.0-00 to 8.5.2-00 inclusive.
-
Verify local authentication is configuredCheck if local user authentication is enabled within HGLM. Review the HGLM security or user management settings to confirm local accounts exist and can access the system.Affected if Local authenticated users can access the HGLM component.
You are affected if you have HPE XP Storage systems running HGLM with a version between 6.3.0-00 and 8.5.2-00 where local authentication is enabled.
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 dataUpdate HGLM to a version beyond 8.5.2-00 (or the latest patched version) following HPE's recommended upgrade path for XP Storage systems. Verify the update in a test environment before production deployment.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8985 — 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-2017-8985 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