CVE-2019-11949
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 · uneditedA 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 confidenceA remote code execution vulnerability exists in HPE Intelligent Management Center (IMC) PLAT versions earlier than 7.3 E0506P09. The CVSS 9.8 score indicates this is a trivially exploitable, network-authenticated RCE flaw affecting this enterprise network management platform.
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< 7.3= 7.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm HPE IMC installationCheck for HPE Intelligent Management Center on the system by searching for installation directories (commonly under C:\hp\imc or C:\Program Files\HP\IMC) or look for the 'hpimc' or 'IMC' service in Windows Services or init scripts on Linux.Affected if HPE IMC is not installed on the system.
-
Locate IMC PLAT version fileNavigate to the IMC installation directory and look for a version file, about dialog, or check the 'version.properties' or 'build.info' file typically found in the core platform directory. Alternatively, access the IMC web console and look for version information in the Help or About section.Affected if The version cannot be determined from the installation.
-
Extract installed PLAT versionRead the version number from the identified version file or web interface. Common locations include the 'plat' or 'core' subdirectory, or the login page footer in the web console.Affected if No version information is displayed or the file is missing.
-
Compare against affected version rangeCompare your extracted version to the affected range: any version lower than 7.3, or exactly version 7.3 (prior to E0506P09 patch). Note the full version string including any patch identifiers like 'E0506P09'.Affected if The installed version is less than 7.3 or is exactly 7.3 without the E0506P09 patch.
The system is affected if HPE Intelligent Management Center PLAT is installed and the version is either below 7.3 or is 7.3 without the E0506P09 patch applied.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.3
Upgrade HPE IMC PLAT to version 7.3 E0506P09 or later to remediate this critical RCE vulnerability.
7.3 E0506P09 or later
- 1. Back up the current HPE Intelligent Management Center configuration and database
- 2. Download HPE IMC version 7.3 E0506P09 or later from the HPE support portal (support.hpe.com)
- 3. Stop all IMC services before applying the upgrade
- 4. Install the IMC 7.3 E0506P09 update following the standard upgrade procedure
- 5. Restart IMC services after the upgrade completes
- 6. Verify the IMC web interface is accessible and all services are running
- 7. Confirm the version by checking About in the IMC PLAT interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11949 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-11949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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