Intelligent Management CenterApplication · Hp

CVE-2017-12504

HIGH · 8.8 CVSS v3.0 Published 2018-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 PLAT 7.3 (E0504) was found. The problem was resolved in HPE Intelligent Management Center PLAT v7.3 (E0506) or any subsequent version.

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

Remote Code Execution vulnerability in HPE Intelligent Management Center (iMC) PLAT version 7.3 (E0504). The vulnerability was addressed in version 7.3 (E0506). No additional technical details about the specific attack vector, exploitation method, or affected component are provided in the official description.

MitigationUpgrade HPE Intelligent Management Center PLAT to version 7.3 (E0506) or any subsequent version to remediate this RCE vulnerability.

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

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

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

  1. Check HPE iMC PLAT version via console
    Access the HPE iMC management console and navigate to the About or System Information section, typically found under Help > About or Administration > System Info. Look for the PLAT version display which shows both the base version (7.3) and the build identifier (such as E0504 or E0506).
    Affected if The displayed version shows 7.3 with build identifier E0504 (any build before E0506). Version 7.3 E0506 or later is not affected.
  2. Check PLAT service version via command line
    Locate the iMC installation directory (commonly in C:\hp\iMC or /opt/hp/imc). Look for version information files in the plat\bin or similar subdirectories. Run any available version check script or examine the plat version file which typically contains the build string.
    Affected if The version file or output shows build E0504 or any build earlier than E0506.
  3. Check PLAT version from Windows Programs and Features
    Open Windows Control Panel > Programs and Features (or Add/Remove Programs). Locate 'HPE Intelligent Management Center PLAT' in the list. The version column displays the full version string including the build identifier.
    Affected if The installed version displays as 7.3 (E0504) specifically, indicating the vulnerable build.
  4. Check PLAT version from Linux package manager
    If iMC PLAT is installed on Linux, use the package management tool: rpm -qa | grep -i imc or dpkg -l | grep -i imc to list installed packages. Examine the package version string which includes the build identifier.
    Affected if The package version shows build E0504 or earlier.

If the installed HPE iMC PLAT version is exactly 7.3 (E0504) or any earlier build within the 7.3 line, the environment is vulnerable to this RCE. Versions 7.3 (E0506) and later are not affected.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HPE Intelligent Management Center PLAT to version 7.3 (E0506) or any subsequent version to remediate this RCE vulnerability.

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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