dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2019-11945

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
High EPSS 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

Critical remote code execution vulnerability in HPE Intelligent Management Center (IMC) PLAT. The vulnerability is network-exploitable and rated 9.8 CVSS, indicating trivial exploitability with complete system compromise potential. Specific technical details of the attack vector (e.g., injection point, authentication requirement) are not provided in the available description.

MitigationUpgrade HPE IMC PLAT to version 7.3 E0506P09 or later. This is a straightforward version upgrade; no complex configuration changes or workarounds are described or recommended.

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 is installed
    Check for HPE Intelligent Management Center in installed programs (Windows: Registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall, or Linux: rpm -qa | grep -i imc or dpkg --list | grep -i imc)
    Affected if HPE IMC PLAT is found on the system
  2. Locate IMC installation directory
    Common paths: C:\Program Files\HPE\imc (Windows) or /opt/hpe/imc (Linux). Check for plat or server subdirectories containing IMC binaries and libraries
    Affected if IMC installation directory exists and contains plat/server components
  3. Determine IMC PLAT version
    Check version file or executable properties: look for version.info, about.html, or right-click imcplat.exe > Properties > Details. Also check the IMC web interface / about page if accessible
    Affected if Installed version is below 7.3 or exactly 7.3
  4. Verify IMC services are running
    Windows: services.msc look for 'HPE IMC' services; Linux: systemctl status imc or ps aux | grep imc
    Affected if IMC services are active (vulnerability is exploitable when service is running)
  5. Check if IMC web interface is exposed
    Verify network listeners: netstat -an | grep 8080 or 443 (default IMC ports). Check firewall rules and.conf files in /conf directory for bind addresses
    Affected if IMC web interface is accessible from network (remote exploit vector)

If HPE IMC PLAT is installed with a version less than 7.3 or exactly 7.3, and the service is accessible over the network, the system is affected by this CVE.

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. This is a straightforward version upgrade; no complex configuration changes or workarounds are described or recommended.

Recommended fix High confidence

7.3 E0506P09

  1. 1. Identify the current HPE IMC PLAT version by accessing the IMC console or checking the system information
  2. 2. Navigate to HPE support website (support.hpe.com) and search for HPE Intelligent Management Center
  3. 3. Locate and download the IMC PLAT version 7.3 E0506P09 or later patch
  4. 4. Back up the current IMC configuration and database according to HPE backup procedures
  5. 5. Stop all IMC services before applying the upgrade
  6. 6. Apply the version 7.3 E0506P09 patch following the HPE upgrade documentation
  7. 7. Restart IMC services and verify the version has been updated
  8. 8. Test core IMC functionality to ensure normal operations
Caveat Review HPE release notes for version 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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