dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2017-5790

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 deserialization of untrusted data vulnerability in HPE Intelligent Management Center (IMC) PLAT version 7.2 E0403P06 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 deserialization vulnerability in HPE Intelligent Management Center PLAT allows unauthenticated remote attackers to execute arbitrary code by sending maliciously crafted serialized Java objects. This stems from the application deserializing untrusted data without proper validation, a well-known vulnerability class (CWE-502).

MitigationApply the vendor patch for HPE IMC PLAT E0403P06 or later. If patching is not immediately possible, restrict network access to IMC management interfaces and disable any unnecessary JMX/RMI endpoints to reduce attack surface.

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. Verify HPE IMC installation and running status
    Check for running IMC processes using task manager or command: tasklist /FI "IMAGENAME eq *.exe" on Windows, or ps aux | grep -i imc on Linux. Also check common installation directories like C:/HP/IMC or /opt/hp/imc.
    Affected if HPE IMC PLAT is installed and running
  2. Determine IMC PLAT version
    Check the version file in the IMC installation directory, typically found in version.properties, about.html, or in the application itself under Help > About. Look specifically for version 7.2.
    Affected if The installed IMC PLAT version equals 7.2 exactly
  3. Identify exposed JMX/RMI endpoints
    Use netstat or similar tool to check if ports commonly used by JMX/RMI (typically 1099, 9004, or custom ports configured during IMC setup) are listening. Check the IMC configuration files for JMX/RMI service enablement.
    Affected if JMX or RMI ports are open and listening on network interfaces
  4. Assess network accessibility of IMC management interface
    Determine if the IMC web console port (default 8080 or 8443) is accessible from untrusted networks. Use nmap, netstat, or firewall rules to identify exposed management ports.
    Affected if IMC management interfaces are reachable from untrusted or external networks without proper network segmentation

A user is affected if HPE IMC PLAT version 7.2 is installed and its JMX/RMI or management interfaces are network-accessible to unauthenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for HPE IMC PLAT E0403P06 or later. If patching is not immediately possible, restrict network access to IMC management interfaces and disable any unnecessary JMX/RMI endpoints to reduce attack surface.

Recommended fix Moderate confidence

HPE IMC PLAT version 7.2 E0504 or later (or IMC 7.3.x/7.4.x if available for your deployment)

  1. 1. Back up the current HPE IMC configuration and database before any upgrade.
  2. 2. Download the fixed version of HPE Intelligent Management Center from the HPE Support Portal (support.hpe.com).
  3. 3. Stop all IMC services on the server.
  4. 4. Install the patched version (7.2 E0504 or later) following the HPE upgrade guide.
  5. 5. After installation, verify all IMC services start successfully.
  6. 6. Confirm the IMC web interface is accessible and functional.
  7. 7. Review HPE security bulletin HPSBGN03671 or equivalent for the complete list of fixed vulnerabilities.
Caveat Review HPE upgrade documentation for compatibility requirements; ensure your operating system and database versions are supported by the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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