Intelligent Management CenterApplication · Hp

CVE-2019-5348

HIGH · 8.8 CVSS v3.0 Published 2019-06-05
Fix available
A fix is available. Upgrade to 7.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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. This network-exploitable flaw allows attackers to execute arbitrary code on affected systems, likely through improper input validation or a code injection flaw in the IMC platform components.

MitigationUpgrade HPE IMC PLAT to version 7.3 E0506P09 or later. If immediate patching is not possible, restrict network access to IMC management interfaces using firewall rules or VPN access controls.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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
    Check if HPE Intelligent Management Center is installed on the system by looking for IMC-related services or processes running (e.g., imcserver, tomcat, or related HPE processes in task manager or service list)
    Affected if HPE IMC is not installed - not affected. If IMC is present, proceed to version check.
  2. Determine installed IMC PLAT version
    Access the IMC management console web interface and navigate to the About or System Information page to view the PLAT version, or check the installation directory for version manifest files if accessible
    Affected if Unable to determine version - treat as potentially affected and investigate further
  3. Compare version against affected range
    Compare your installed PLAT version to the affected versions: any version lower than 7.3, or exactly version 7.3, is vulnerable. The fixed version is 7.3 E0506P09.
    Affected if Version is < 7.3 or equals 7.3 - system is affected by this vulnerability
  4. Assess network exposure of IMC interface
    Determine if the IMC web management console (typically ports 8080, 8443, or similar) is accessible from untrusted networks by checking firewall rules, exposed network interfaces, and listening ports on the IMC server
    Affected if IMC management interface is exposed to untrusted networks without VPN or firewall protection - exploitation is possible from remote attackers
  5. Check for suspicious IMC activity
    Review IMC server logs and network traffic for signs of injection attempts or unauthorized command execution, such as unexpected scripts, unusual query parameters in web logs, or unauthorized process creation
    Affected if Evidence of injection attempts or unauthorized code execution in logs - indicates potential exploitation

System is affected if HPE IMC PLAT version is 7.3 or any version below 7.3 AND the IMC 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
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 possible, restrict network access to IMC management interfaces using firewall rules or VPN access controls.

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-5348 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