dbcve.org
Xp7 Device ManagerApplication · Hp

CVE-2019-5408

MEDIUM · 6.5 CVSS v3.0 Published 2019-08-09
Fix available
A fix is available. Upgrade to 8.6.1-02 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Command View Advanced Edition (CVAE) products contain a vulnerability that could expose configuration information of hosts and storage systems that are managed by Device Manager server. This problem is due to a vulnerability in Device Manager GUI. The following products are affected. DevMgr version 7.0.0-00 to earlier than 8.6.1-02 RepMgr if it is installed on the same machine as DevMgr TSMgr if it is installed on the same machine as DevMgr. The resolution is to upgrade to the fixed version as described below or later version of DevMgr 8.6.2-02 or later. RepMgr and TSMgr will be corrected by upgrading DevMgr.

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 confidence

This is an information disclosure vulnerability in the Device Manager GUI component of HPE Command View Advanced Edition. The flaw allows unauthorized access to configuration data of hosts and storage systems managed by the Device Manager server, likely through improper access controls in the web interface.

MitigationUpgrade Device Manager to version 8.6.2-02 or later. RepMgr and TSMgr vulnerabilities are resolved by upgrading DevMgr since they share the same installation.

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
Xp7 Device ManagerApplication
Affected:>= 7.0.0-00, < 8.6.1-02
Xp7 Replication ManagerApplication
Affected:all versions
Xp7 Tiered Storage ManagerApplication
Affected:all versions

CVSS 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
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if HPE Command View Advanced Edition components are installed
    Look for installation directories or installed programs related to HPE Command View, Device Manager, Replication Manager, or Tiered Storage Manager. On Windows, check Add/Remove Programs or the installation path (commonly C:\Program Files\HPE\ or similar). On Linux, check /opt/hpe/ or use rpm/dpkg queries.
    Affected if Any of these components are present on the system
  2. Determine the installed Device Manager version
    Locate the Device Manager version information. This is typically found in the GUI about page, in an installation log file, or in a version file within the installation directory. Check the main Device Manager server installation for a version file or use the GUI's Help > About function if accessible.
    Affected if The installed version is 7.0.0-00 or higher but lower than 8.6.1-02
  3. Check if Replication Manager or Tiered Storage Manager are installed
    Verify whether Hp Xp7 Replication Manager or Hp Xp7 Tiered Storage Manager are installed on the same system as Device Manager. These share the same installation as Device Manager.
    Affected if Either Replication Manager or Tiered Storage Manager is installed (all versions are affected)
  4. Confirm the Device Manager web GUI is accessible
    Verify that the Device Manager web interface is enabled and accessible. This vulnerability exploits improper access controls in the web interface, so the web service must be running for exploitation to be possible.
    Affected if The Device Manager web interface is exposed and accessible to users or networks where unauthorized access is possible

The environment is affected if HPE Command View Advanced Edition Device Manager version is 7.0.0-00 through 8.6.0-xx (any version before 8.6.1-02), or if Replication Manager or Tiered Storage Manager are installed, and the web GUI is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 8.6.1-02 or later
Fixed in 8.6.1-02
Interim mitigation

Upgrade Device Manager to version 8.6.2-02 or later. RepMgr and TSMgr vulnerabilities are resolved by upgrading DevMgr since they share the same installation.

Fix this in Xp7 Device Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5408 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5408 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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