dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2019-11944

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 allows unauthenticated remote attackers to execute arbitrary code on affected systems due to insufficient input validation in the IMC platform.

MitigationUpgrade HPE IMC PLAT to version 7.3 E0506P09 or later. If immediate patching is not possible, restrict network access to IMC management interfaces and implement additional network segmentation.

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. Identify if HPE IMC is installed
    Check for the presence of HPE Intelligent Management Center on the system by looking for the IMC service or process, typically named 'iMC' or 'HPE IMC' in Windows Services or running processes.
    Affected if The HPE IMC service or process is found running on the system
  2. Locate the IMC installation directory
    Common default paths include C:\Program Files\HP\iMC or C:\Program Files\Hewlett Packard Enterprise\iMC. Check the version.xml or a similar version file in the installation directory.
    Affected if IMC is installed in a directory that contains version information earlier than E0506P09
  3. Determine the installed IMC PLAT version
    Open the version file or check the product information typically found in the IMC installation directory. Look for the full version string which should include the build number such as E0506P09.
    Affected if The version displayed is < 7.3 or equals 7.3 without the E0506P09 build or later
  4. Verify the exact build version
    If the version shows 7.3, confirm whether the build is E0506P09 or later. Earlier builds of version 7.3 are affected.
    Affected if The build is earlier than E0506P09 or the version is any 7.3.x build preceding E0506P09
  5. Check if the IMC management interface is exposed
    Determine if the IMC web interface (typically on port 8080 or 8443) is accessible from network locations. This is the attack vector for unauthenticated remote exploitation.
    Affected if The IMC web management interface is reachable from untrusted networks

The system is affected if HPE IMC is installed with a version earlier than 7.3 E0506P09, or at exactly version 7.3 without the E0506P09 patch, and the management interface is network-accessible.

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 possible, restrict network access to IMC management interfaces and implement additional network segmentation.

Recommended fix High confidence

HPE Intelligent Management Center 7.3 E0506P09

  1. Back up the current HPE Intelligent Management Center configuration and database
  2. Review HPE IMC 7.3 E0506P09 release notes for any specific upgrade prerequisites
  3. Download HPE Intelligent Management Center version 7.3 E0506P09 from the HPE support portal (support.hpe.com)
  4. Schedule a maintenance window as upgrades may require service downtime
  5. Stop all IMC services before beginning the upgrade process
  6. Install version 7.3 E0506P09 following the HPE upgrade documentation
  7. Verify all IMC services start successfully after upgrade
  8. Confirm the IMC web interface is accessible and functioning

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 / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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