CVE-2019-5390
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 command injection 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 command injection vulnerability in HPE Intelligent Management Center (IMC) PLAT allows unauthenticated attackers to execute arbitrary OS commands on the target system via specially crafted input, potentially leading to 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.
-
Identify HPE IMC PLAT installationLocate HPE Intelligent Management Center installation directory or check system services for 'IMC' or 'Intelligent Management Center' processesAffected if HPE IMC PLAT is installed on the system
-
Determine IMC PLAT versionAccess IMC web console and navigate to 'System > License' or 'System > About' page to view the exact version number, or check installation logs/version files in the IMC installation directoryAffected if Version is less than 7.3 or exactly equals 7.3
-
Confirm version is within affected rangeCompare installed version against affected ranges: versions < 7.3 or = 7.3 are vulnerable; versions > 7.3 (such as 7.3 E0506P09 or later) are not affectedAffected if Installed version is 7.3 or any version below 7.3
User is affected if HPE Intelligent Management Center PLAT is installed and the version is 7.3 or any version below 7.3, as this enables the unauthenticated command injection attack surface.
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 the IMC management interface and implement input validation at network boundaries.
HPE IMC PLAT version 7.3 E0506P09 or later
- 1. Identify the current HPE IMC PLAT version by accessing the IMC console and navigating to the About or System Information section
- 2. Compare your current version against the vulnerable versions (anything earlier than 7.3 E0506P09, including base version 7.3)
- 3. Download the fixed version (7.3 E0506P09 or later) from the HPE support portal at support.hpe.com
- 4. Review HPE's upgrade documentation and release notes for IMC before proceeding
- 5. Perform a full backup of the IMC database and configuration
- 6. Stop all IMC services before applying the upgrade
- 7. Install version 7.3 E0506P09 or the latest stable release
- 8. Verify the upgrade was successful by checking the IMC version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5390 — 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-5390 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