Intelligent Management CenterApplication · Hp

CVE-2017-5815

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-15
Fix available
A fix is available. Upgrade to 7.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A Remote Code Execution vulnerability in HPE Intelligent Management Center (iMC) PLAT version 7.3 E0504P04 was found.

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 confidence

A Remote Code Execution vulnerability exists in HPE Intelligent Management Center (iMC) PLAT version 7.3 E0504P04. The specific vulnerability type and attack vector are not detailed in available documentation, but the critical CVSS score of 9.8 indicates trivial exploitability allowing unauthenticated remote attackers to execute arbitrary code on affected systems.

MitigationApply the HPE security patch for iMC PLAT 7.3 E0504P04 or upgrade to a patched version as provided by HPE's security advisory. Restrict network access to iMC management interfaces to trusted sources until patching is complete.

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
Intelligent Management CenterApplication
Affected:< 7.3= 7.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm HPE iMC PLAT installation
    Locate HPE Intelligent Management Center on the system by checking installed programs, services, or the default installation directory. Verify the PLAT component is present.
    Affected if HPE iMC PLAT is installed on the system
  2. Identify iMC PLAT version
    Use the system's software inventory, iMC administrative console, or version information files to determine the exact PLAT version number.
    Affected if The version is 7.3 or any version below 7.3
  3. Verify the E0504P04 patch status
    Check if the E0504P04 patch has been applied by reviewing the iMC patch history, version string, or HPE support documentation for the installed build.
    Affected if The installed version is 7.3 without the E0504P04 patch applied
  4. Assess network exposure
    Review firewall rules and network configuration to determine if the iMC management interface is accessible from untrusted networks.
    Affected if The iMC management port is exposed to untrusted or public networks

The environment is affected if HPE iMC PLAT version 7.3 or any version below 7.3 is installed and the management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.3 or later
Fixed in 7.3
Interim mitigation

Apply the HPE security patch for iMC PLAT 7.3 E0504P04 or upgrade to a patched version as provided by HPE's security advisory. Restrict network access to iMC management interfaces to trusted sources until patching is complete.

Recommended fix Moderate confidence

HPE iMC PLAT version 7.3 E0504P07 or later

  1. 1. Back up the current HPE iMC configuration and database to ensure data preservation.
  2. 2. Download HPE Intelligent Management Center version 7.3 E0504P07 or later from the official HPE support portal (support.hpe.com).
  3. 3. Stop all iMC services on the affected server before applying the update.
  4. 4. Apply the hotfix patch E0504P07 (or latest available) following the installation instructions in the HPE support documentation.
  5. 5. Restart iMC services and verify the application is functioning normally.
  6. 6. Confirm the vulnerability is remediated by checking the iMC version information.
Caveat Review HPE release notes for this patch to check for any configuration changes or compatibility considerations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5815 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5815 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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