CVE-2019-5369
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 versions earlier than 7.3 E0506P09. The vulnerability allows attackers to execute arbitrary code on the affected system remotely, likely through improper input validation or insecure deserialization in the IMC platform components.
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 IMC installation directories (typically C:\hp\imc or C:\Program Files\HP\IMC) or look for the 'HP Intelligent Management Center' service running on the system.Affected if HPE IMC is not installed on the system.
-
Locate IMC version fileNavigate to the IMC installation directory and look for a version file (commonly version.properties, about.html, or in the /bin directory). Alternatively, access the IMC web console and check the About or System Information page.Affected if Unable to locate version information.
-
Identify installed IMC PLAT versionRead the version file or web console information. Note the full version string including any patch level (for example: 7.3, 7.2, 7.3 E0506P09).Affected if Version information cannot be determined.
-
Compare version against affected rangeCompare your installed version to the affected versions: any version earlier than 7.3, or version 7.3 without the E0506P09 patch. The fixed version is 7.3 E0506P09 or later.Affected if Installed version is earlier than 7.3, or is 7.3 without the E0506P09 patch.
-
Check if IMC web services are exposedVerify if the IMC web interface (typically on port 8080 or 8443) is accessible from network segments accessible to potential attackers. Check firewall rules and network access controls.Affected if IMC web interface is exposed to untrusted networks without proper segmentation.
A user is affected if HPE IMC PLAT is installed and the version is earlier than 7.3 E0506P09 (including any 7.3 version without that specific patch).
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. Prior to upgrade, ensure proper backups and maintenance windows are planned.
- Consultation4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5369 — 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-5369 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