CVE-2019-5361
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 affecting versions prior to 7.3 E0506P09. The vulnerability has a CVSS score of 8.8 (HIGH), indicating significant risk if exploited.
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 installationCheck for HPE Intelligent Management Center installation by searching for IMC-related directories or services. Common paths include C:\hp\imc\ or /opt/hp/imc/. On Windows, verify in Add/Remove Programs or check services for 'HP IMC' services.Affected if HPE IMC is installed on the system
-
Locate IMC PLAT version fileNavigate to the IMC installation directory and locate the version file. The version information is typically stored in a version.properties, version.txt, or similar file within the PLAT installation folder, often under plat\conf\ or the root IMC directory.Affected if The version file exists and can be read
-
Extract installed IMC PLAT versionOpen the version file and identify the full version string. Look for version patterns like 7.3, 7.2, 7.1, etc. The fixed version is 7.3 E0506P09 - note the E0506P09 patch identifier.Affected if Version displays as 7.3 (any sub-version) or any version below 7.3
-
Compare against affected version rangeParse the version string and compare: versions < 7.3 are affected, version = 7.3 is affected unless it includes patch E0506P09 or later.Affected if Installed version is 7.3 without E0506P09, or any version below 7.3 (e.g., 7.2, 7.1, 5.x)
-
Check if IMC web interface is accessibleVerify if the IMC web console port (typically port 8080 or 8443) is listening and accessible. Check network listeners using 'netstat -an' or by attempting to reach the web interface URL.Affected if The IMC web interface is exposed and the version is in the affected range
A system is affected if HPE Intelligent Management Center PLAT is installed with version 7.3 (without E0506P09 patch) or any version prior to 7.3, and the IMC web interface is 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.
From vendor data7.3
Apply HPE vendor patch version 7.3 E0506P09 or later to resolve the RCE vulnerability. Upgrade procedures should follow HPE's official documentation for IMC PLAT.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.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 $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5361 — 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-5361 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