CVE-2019-5360
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 in versions earlier than 7.3 E0506P09. The vulnerability is exploitable remotely and allows an attacker to execute arbitrary code on the affected system. IMC PLAT is a network management platform, making this a critical infrastructure vulnerability.
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 installedLook for HPE Intelligent Management Center in installed programs (Windows: Programs and Features, Linux: check /opt/iMC or similar installation directories)Affected if HPE IMC PLAT is present on the system
-
Locate the IMC PLAT version fileNavigate to the IMC installation directory and find the version information file, typically in conf/version.properties or check the imc.exe file properties for version detailsAffected if Unable to locate version information indicates unknown IMC installation
-
Determine the installed IMC PLAT versionRead the version number from the version file or use the IMC PLAT client UI: Help > About to display the full version string including build/patch level (e.g., 7.3 E0506P09)Affected if Version displays as any build earlier than 7.3 E0506P09, or shows only 7.3 without the E0506P09 suffix
-
Compare against vulnerable version rangeCheck if the version is < 7.3 or equals 7.3 without the E0506P09 patch level appliedAffected if Installed version is 7.3 (without E0506P09) or any version earlier than 7.3
The environment is affected if HPE Intelligent Management Center PLAT is installed with any version earlier than 7.3 E0506P09
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 Intelligent Management Center (IMC) PLAT to version 7.3 E0506P09 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the IMC management interfaces and implement additional monitoring for suspicious activity.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5360 — 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-5360 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