CVE-2019-5377
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 affecting versions earlier than 7.3 E0506P09. The vulnerability allows remote attackers to execute arbitrary code on affected installations, likely through unauthenticated network access to the IMC platform.
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.
-
Identify HPE IMC installationCheck if HPE Intelligent Management Center is deployed in the environment by querying installed software listings, reviewing system inventory, or identifying running processes related to IMC (such as imc.exe, imcServer, or associated services).Affected if HPE IMC is present on the system
-
Determine IMC PLAT versionAccess the IMC platform management console or use the product's built-in version checking mechanism (typically found in About or System Information sections of the web UI, or via command line tools provided with IMC).Affected if Unable to determine the version or version shows as 7.3 or earlier
-
Compare installed version to affected rangesReview the identified version against the affected ranges: any version earlier than 7.3, or exactly version 7.3 (without the E0506P09 patch) is vulnerable. Versions 7.3 E0506P09 or later are not affected.Affected if Installed version is 7.3 or earlier (the affected range is < 7.3 OR = 7.3)
-
Assess network exposure of IMC management interfaceDetermine if the IMC management interfaces (typically ports 8080, 8443, or the web UI port) are accessible from untrusted networks or the internet. Review firewall rules and network segmentation configurations.Affected if Management interface is exposed to unauthenticated or untrusted network access
If HPE IMC PLAT version 7.3 or earlier is installed and its management interface is network-accessible, the environment is vulnerable to remote code execution via this CVE.
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 IMC PLAT to version 7.3 E0506P09 or later. If immediate upgrading is not feasible, restrict network access to IMC management interfaces and implement additional authentication layers.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5377 — 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-5377 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