CVE-2019-5349
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 platform affecting versions earlier than 7.3 E0506P09. The vulnerability allows unauthenticated remote attackers to execute arbitrary code on the affected system due to insufficient input validation in the platform component.
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 installedCheck for HPE Intelligent Management Center installation by looking for the IMC program directory (commonly at C:\hp\imc or C:\Program Files\HP\HP IMC) or the IMC service running on the systemAffected if HPE IMC PLAT is not installed on the system
-
Locate the IMC PLAT version fileNavigate to the IMC installation directory and locate the version information file (typically in the plat or bin subdirectory, often named version.properties, version.ini, or accessible via the IMC client web interface)Affected if Unable to locate version information indicates IMC may not be properly installed
-
Extract the installed IMC PLAT versionOpen the version file or access the IMC web console and retrieve the exact version string (format is typically 7.3 followed by the patch level such as E0506P09)Affected if No version string is returned from the IMC installation
-
Compare version against affected rangeCompare your extracted version to the affected versions: any version earlier than 7.3, or version 7.3 before patch E0506P09. Versions 7.3 E0506P09 and later are not affectedAffected if Installed version is < 7.3 OR installed version is 7.3 without E0506P09 patch level
-
Verify platform component network exposureCheck if the IMC PLAT web interface (typically port 8080 or 8443) is accessible from untrusted networks. Review firewall rules and network segmentation surrounding the IMC serverAffected if The IMC platform component is reachable from untrusted networks and version is within the affected range
You are affected if HPE IMC PLAT is installed with a version earlier than 7.3 E0506P09 and the platform component is network-accessible to untrusted sources.
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 PLAT to version 7.3 E0506P09 or later to remediate this vulnerability. If immediate upgrade is not feasible, restrict network access to the IMC management interface to trusted sources only.
- Consultation8.0 h
- Implementation4.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5349 — 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-5349 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