CVE-2019-5367
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. The CVSS 9.8 indicates a network-exploitable flaw requiring no authentication, allowing complete system compromise.
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 is installedCheck Windows Programs and Features for 'HPE Intelligent Management Center' or look for the IMC installation directory (typically Program Files\HPE\IMC)Affected if The product is not present on the system
-
Retrieve the IMC PLAT versionLocate the version information in the IMC installation directory or check the Windows service properties for the 'iMC Platform' serviceAffected if The installed version cannot be determined
-
Compare version to affected rangeMatch the exact version string (such as 7.2, 7.3, or 7.3 E0506P09) against the vulnerable range: versions earlier than 7.3 E0506P09 or equal to 7.3Affected if The version is 7.3 or any release earlier than 7.3 E0506P09
-
Verify network accessibilityConfirm whether the IMC management interface (typically ports 8080, 8443, or 443) is listening on non-localhost network interfaces and exposed to untrusted networksAffected if The IMC management console is reachable from network attackers
Environment is affected if HPE IMC PLAT is installed with version 7.3 or any version earlier than 7.3 E0506P09 and the management interface is network-accessible
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. If immediate patching is not possible, restrict network access to IMC management interfaces.
HPE IMC version 7.3 E0506P09 or later
- Backup the HPE Intelligent Management Center database and configuration files
- Download HPE IMC version 7.3 E0506P09 (or later) from support.hpe.com
- Stop the IMC services before applying the upgrade
- Follow HPE's documented upgrade procedure for IMC 7.3
- Restart IMC services after the upgrade completes
- Verify the IMC web interface is accessible and functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5367 — 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-5367 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