CVE-2019-5341
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 confidenceCVE-2019-5341 is a remote code execution vulnerability in HPE Intelligent Management Center (IMC) PLAT. The vulnerability is network-exploitable (CVSS 8.8 indicates low attack complexity with no privileges required). Affected versions are earlier than IMC PLAT version 7.3 E0506P09.
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 installedIdentify if HPE Intelligent Management Center is deployed in your environment. Check for processes named 'imc' or 'HPE IMC' running on servers, or look for the IMC management interface accessible on network ports commonly used by IMC (typically TCP ports 8080, 8443, or 80/443 for web UI).Affected if HPE IMC PLAT is present in the environment.
-
Determine installed IMC PLAT versionAccess the IMC web management console and navigate to the About or System Information page, typically found under 'System' > 'System Overview' or similar. Alternatively, check version information from the IMC server's installation directory if you have filesystem access.Affected if The displayed version is earlier than 7.3 E0506P09, or shows version 7.3 without the E0506P09 update.
-
Check if IMC management interface is network-exposedScan your network boundaries to determine if the IMC web UI ports (8080, 8443, or 80/443) are accessible from untrusted networks or the internet. Use network scanning tools or review firewall rules to identify exposed management interfaces.Affected if The IMC management interface is reachable from networks outside the trusted management zone.
-
Verify IMC PLAT services are runningOn the IMC server, check if the core IMC Platform service (often named 'imcplat' or similar) is actively running. This is the component that contains the vulnerability.Affected if The IMC PLAT service is running and the version is within the affected range.
You are affected if HPE Intelligent Management Center PLAT is installed and the version is earlier than 7.3 E0506P09, regardless of whether the management interface is network-exposed (the flaw is exploitable remotely with no authentication).
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. If immediate upgrade is not possible, restrict network access to IMC management interfaces and implement additional network segmentation as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5341 — 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-5341 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