dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2017-5804

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A Remote Code Execution vulnerability in HPE Intelligent Management Center (iMC) PLAT version 7.2 was found.

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 confidence

A Remote Code Execution vulnerability exists in HPE Intelligent Management Center (iMC) PLAT version 7.2. The vulnerability allows unauthenticated attackers to execute arbitrary code on the affected system due to improper input validation. As a network management platform, iMC typically has high privileges on the network, making this critical vulnerability particularly dangerous.

MitigationApply the appropriate HPE security patch for iMC PLAT 7.2. If no patch is available, consider network segmentation to limit exposure and disable unnecessary iMC services until remediation is possible.

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
Intelligent Management CenterApplication
Affected:= 7.2

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
High
Integrity
High
Availability
High

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

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

  1. Identify HPE iMC PLAT installation and version
    Locate the HPE Intelligent Management Center installation directory and check the version information in the product's about or version details. Common locations include C:\hp\iMC or C:\Program Files\HPE\iMC. Look for version.txt, version.ini, or use the iMC management console to view version information.
    Affected if The installed version is exactly 7.2 (matches CVE-2017-5804 affected version)
  2. Confirm iMC PLAT service is running
    Check if the HPE iMC Platform service (typically named 'hpimcplat' or 'iMC PLAT') is running on the system. Use Windows Services console (services.msc) or command 'sc query hpimcplat' to verify service status.
    Affected if The iMC PLAT service is running, making the vulnerable component active
  3. Identify listening ports for iMC services
    Use netstat or a port scanner to identify ports where iMC services are listening. iMC typically uses ports 8080, 8443, or 8000-series ports for its web console. Run 'netstat -an | findstr "8080\|8443\|8000"' to list relevant listeners.
    Affected if iMC web services are exposed on accessible network ports, making the unauthenticated vulnerability reachable
  4. Check for web console accessibility
    Attempt to access the iMC web interface via browser to confirm the management platform is operational. The default URL is typically https://localhost:8443 or http://localhost:8080. Verify the login page or service responds.
    Affected if The iMC web console is accessible and responding, confirming the vulnerable service is active
  5. Review network exposure of iMC management interface
    Determine if the iMC server is directly accessible from untrusted networks. Check firewall rules, network segmentation, and whether the management ports are exposed to the internet or untrusted VLANs.
    Affected if The iMC management interface is reachable from untrusted networks, enabling unauthenticated attackers to exploit the vulnerability

A system is affected if HPE Intelligent Management Center PLAT version 7.2 is installed with the service running and its management interface is network-accessible to potential attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate HPE security patch for iMC PLAT 7.2. If no patch is available, consider network segmentation to limit exposure and disable unnecessary iMC services until remediation is possible.

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5804 — 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-2017-5804 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