dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2019-5352

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) PLAT versions earlier than 7.3 E0506P09. The vulnerability is rated critical with a CVSS score of 9.8, indicating trivial exploitability and severe impact to confidentiality, integrity, and availability.

MitigationUpgrade HPE IMC PLAT to version 7.3 E0506P09 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to IMC management interfaces and implement additional monitoring for Indicators of Compromise.

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. Verify HPE Intelligent Management Center is installed
    Check system inventory, installed software list, or look for IMC-related processes/services on the system
    Affected if HPE IMC PLAT software is present on the system
  2. Identify the installed IMC PLAT version
    Use the IMC client or admin interface to access system information, or check the installation directory for version files. Common methods include: accessing Help > About in the IMC client, checking the imc.ini or version.xml files in the installation directory, or running 'imc -version' if a command-line tool exists.
    Affected if The version returned is 7.3 or any version lower than 7.3
  3. Confirm the exact patch level for version 7.3
    If version 7.3 is reported, check whether it is specifically E0506P09 or later. Review release notes, patch documentation, or the exact version string displayed in the IMC admin interface.
    Affected if Version is exactly 7.0, 7.1, 7.2, or 7.3 without the E0506P09 patch applied
  4. Verify network exposure of IMC management interfaces
    Review firewall rules and network configurations to determine if IMC management ports (typically 8080, 8443, or as configured) are accessible from untrusted networks
    Affected if IMC management interfaces are exposed to the internet or untrusted internal segments

A system is affected if HPE IMC PLAT version is 7.3 or any version earlier than 7.3, and the E0506P09 patch has not been applied to version 7.3.

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 to remediate this vulnerability. If immediate patching is not possible, restrict network access to IMC management interfaces and implement additional monitoring for Indicators of Compromise.

Recommended fix Moderate confidence

7.3 E0506P09

  1. Back up the current HPE IMC configuration and database to ensure data can be restored if needed
  2. Verify the current HPE IMC PLAT version is below 7.3 E0506P09 by accessing the IMC web interface or using version check commands
  3. Download the fixed version 7.3 E0506P09 from the HPE Support website (support.hpe.com) using your HPE account credentials
  4. Review the HPE IMC upgrade guide for version 7.3 to understand any prerequisites such as system requirements, compatible browsers, or dependent component updates
  5. Schedule a maintenance window as upgrades may require service downtime
  6. Stop all IMC services or follow the documented shutdown procedure before applying the upgrade
  7. Install version 7.3 E0506P09 following the HPE-provided installation instructions
  8. Restart IMC services after the upgrade completes successfully

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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