CVE-2019-5382
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 confidenceRemote code execution vulnerability in HPE Intelligent Management Center (IMC) PLAT versions earlier than 7.3 E0506P09. An attacker can execute arbitrary code on the affected system due to insufficient input validation or insecure deserialization in the platform component.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm HPE IMC PLAT is installedCheck for HPE Intelligent Management Center installation by looking for the service process 'iMC' or the installation directory (typically under C:\Program Files\HPE\imc or /opt/hp/imc). On Windows, use Services.msc to look for 'HPE IMC Platform' service.Affected if HPE IMC PLAT is not installed on the system.
-
Retrieve IMC PLAT versionAccess the IMC web console and navigate to the 'About' or 'System Information' page to view the PLAT component version. Alternatively, check the version file in the IMC installation directory if accessible.Affected if Unable to retrieve version information.
-
Compare version against affected rangeCheck if the PLAT version is < 7.3 or equals 7.3. The specific safe version is 7.3 E0506P09. Any version before E0506P09 within the 7.3 branch, or any version below 7.3, is affected.Affected if Installed version is 7.3 (any build before E0506P09) or any version lower than 7.3.
-
Verify platform component is in useConfirm the PLAT (Platform) component is enabled by checking the IMC console for platform services. This vulnerability affects the platform component specifically.Affected if PLAT component is not present or disabled.
-
Check network exposure of IMC management interfaceDetermine if the IMC web console (default ports 8080, 8443) is accessible from untrusted networks. Review firewall rules and network segmentation for the IMC management ports.Affected if IMC management interface is exposed to untrusted networks without proper access controls.
The system is affected if HPE IMC PLAT version is below 7.3 E0506P09 (including version 7.3 without the P09 patch) and the PLAT component is enabled.
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.
From vendor data7.3
Upgrade HPE IMC PLAT to version 7.3 E0506P09 or later to remediate the vulnerability. If immediate patching is not possible, restrict network access to the IMC management interface and implement additional monitoring.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5382 — 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-5382 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