dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2019-5358

CRITICAL · 9.8 CVSS v3.0 Published 2019-06-05
Fix available
A fix is available. Upgrade to 7.3 or later.
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 was identified in HPE Intelligent Management Center (IMC) PLAT earlier than version 7.3 E0506P09.

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) Platform (PLAT) in versions earlier than 7.3 E0506P09. The vulnerability is exploitable remotely with CVSS 9.8 critical severity, indicating network-level exploitation likely without authentication, allowing attackers to execute arbitrary code on affected IMC deployments.

MitigationUpgrade HPE IMC PLAT to version 7.3 E0506P09 or later. If immediate patching is not feasible, restrict network access to IMC management interfaces using firewall rules or VPN access controls until the upgrade can be applied.

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.3= 7.3

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. Confirm HPE IMC installation exists
    Check for HPE Intelligent Management Center installation directories or running services on the system. Look for IMC-related processes or the presence of IMC installation folders in Program Files.
    Affected if HPE IMC is installed on the system
  2. Identify IMC Platform version
    Locate the version information for the IMC Platform (PLAT) component. This is typically found in the IMC installation directory, in version files, or accessible via the IMC administrative console under system information.
    Affected if The installed version is 7.3 (any subversion) or any version earlier than 7.3 E0506P09
  3. Verify the specific PLAT build
    Check the exact build or patch level of the IMC Platform component. The affected version includes 7.3 base version, and the fix is specifically version 7.3 E0506P09.
    Affected if The PLAT version does not show E0506P09 or later build identifier
  4. Assess network exposure of IMC management interface
    Determine if the IMC management interface (typically ports 8080, 8443, or other HTTP/HTTPS management ports) is exposed to untrusted networks or the internet. Check firewall rules and network accessibility.
    Affected if The IMC management interface is reachable from untrusted network segments or directly from the internet

The environment is affected if HPE IMC Platform is installed and the version is 7.3 (any build) or earlier than 7.3 E0506P09, regardless of network exposure since exploitation can occur remotely without authentication.

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

Upgrade HPE IMC PLAT to version 7.3 E0506P09 or later. If immediate patching is not feasible, restrict network access to IMC management interfaces using firewall rules or VPN access controls until the upgrade can be applied.

Recommended fix High confidence

HPE IMC PLAT version 7.3 E0506P09 or later

  1. 1. Back up the current HPE IMC configuration and database according to HPE backup procedures
  2. 2. Navigate to support.hpe.com and download HPE Intelligent Management Center version 7.3 E0506P09 or later
  3. 3. Follow HPE's documented upgrade procedure for IMC, ensuring the system is powered and network connectivity is stable during the upgrade
  4. 4. After upgrade completes, verify the IMC services are running correctly
  5. 5. Log in to the IMC console and confirm the version reflects 7.3 E0506P09 or later
  6. 6. Test critical management functions to ensure the upgrade did not disrupt normal operations
Caveat Review HPE release notes for 7.3 E0506P09 for any configuration or compatibility changes before upgrading

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

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 the upgrade done

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-2019-5358 — 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-5358 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