CVE-2019-5391
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 stack buffer overflow 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 · high confidenceA stack buffer overflow vulnerability exists in HPE Intelligent Management Center (IMC) PLAT versions prior to 7.3 E0506P09. This memory corruption vulnerability allows an attacker to overwrite stack memory beyond allocated buffers, potentially leading to arbitrary code execution or denial of service.
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.
-
Locate HPE IMC PLAT installation directoryCheck the default installation path (typically C:\Program Files\HP\iMC\ or /opt/hp/imc/) or use system search for 'imc' installation folders. Identify the platform (PLAT) component.Affected if HPE IMC PLAT is installed on the system
-
Find the installed version numberOpen the imc/platform/conf/version.ini or version.xml file in the installation directory, or access the HPE IMC web console and navigate to Help > About to view the PLAT version.Affected if The displayed version is 7.3 or any version lower than 7.3 (e.g., 7.2, 7.1, 7.0, etc.)
-
Confirm the exact patch levelIf version shows 7.3, check the full version string for the E0506P09 patch identifier in the version details or release notes file within the installation directory.Affected if The version is 7.3 without the E0506P09 patch applied, or is any version < 7.3
-
Verify the IMC PLAT service is runningCheck if the 'iMC PLAT' or 'HP IMC Platform' Windows service is in Running state, or verify the imcPlat process is active on Linux systems.Affected if The vulnerable PLAT service is actively running and accessible on the network
You are affected if HPE IMC PLAT version is 7.3 (without E0506P09 patch) or any version lower than 7.3, and the PLAT service is running.
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 resolve the stack buffer overflow vulnerability.
HPE IMC version 7.3 E0506P09 or later
- 1. Back up the HPE Intelligent Management Center configuration and database before performing any upgrade.
- 2. Download HPE IMC version 7.3 E0506P09 or later from the HPE support portal (support.hpe.com).
- 3. Stop all IMC services on the server.
- 4. Install the IMC 7.3 E0506P09 update following HPE's upgrade documentation.
- 5. Verify the installation completed successfully by checking the IMC version in the web interface.
- 6. Start IMC services and confirm normal operation.
- 7. Validate that the vulnerability is no longer present using appropriate vulnerability scanning.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-5391 — 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-5391 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