CVE-2019-5347
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 authentication bypass 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 authentication bypass vulnerability in HPE Intelligent Management Center (IMC) PLAT allows attackers to circumvent authentication mechanisms and gain unauthorized access to the management platform without valid credentials.
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.
-
Confirm HPE IMC is installedCheck system for HPE Intelligent Management Center installation by looking for the application in installed programs (Windows) or checking common installation directories such as C:\hp\imc or /opt/hp/imcAffected if HPE IMC is not installed on the system - no action needed
-
Identify IMC PLAT versionLocate the IMC PLAT component version file or use the IMC administration console to view version information under System > License & Version or similar version status menuAffected if The displayed version is less than 7.3 or exactly 7.3 (versions prior to 7.3 E0506P09 are affected)
-
Verify IMC web service is accessibleCheck if the IMC web interface (typically on port 8080 or 8443) is exposed and responding by accessing the login page via browser or curl commandAffected if The IMC web service is running and the version is vulnerable (less than 7.3 E0506P09)
-
Review authentication configurationAccess the IMC PLAT security settings through the management console to confirm the authentication mechanism is enabled and check for any unexpected user accounts or configuration changesAffected if The authentication bypass is actively exploitable when the management interface is accessible on the network
If HPE IMC PLAT is installed and the version is less than 7.3 E0506P09 or exactly 7.3, the system is vulnerable to authentication bypass and should be investigated further.
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 to remediate this critical authentication bypass vulnerability.
7.3 E0506P09 or later
- Download HPE Intelligent Management Center version 7.3 E0506P09 or later from support.hpe.com
- Review the HPE IMC upgrade documentation for your current version
- Backup the current IMC configuration and database
- Stop all IMC services before upgrading
- Run the upgrade installer with appropriate administrative privileges
- Verify all services start successfully after upgrade
- Validate that the authentication bypass vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5347 — 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-5347 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