Intelligent Management CenterApplication · Hp

CVE-2020-7160

CRITICAL · 9.8 CVSS v3.1 Published 2020-10-19
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 iccselectdeviceseries expression language injection remote code execution vulnerability was discovered in HPE Intelligent Management Center (iMC) version(s): Prior to iMC PLAT 7.3 (E0705P07).

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 critical expression language injection vulnerability in HPE Intelligent Management Center's iccselectdeviceseries component allows remote attackers to execute arbitrary code by injecting malicious expressions. The vulnerability affects all versions prior to iMC PLAT 7.3 (E0705P07) and can be exploited without authentication due to the critical severity (CVSS 9.8).

MitigationUpgrade HPE iMC to PLAT 7.3 (E0705P07) or later to patch the vulnerability. If immediate upgrade is not feasible, restrict network access to the iMC management interface using firewall rules or network segmentation.

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.1/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. Identify if HPE iMC is installed
    Check for HPE Intelligent Management Center processes running (e.g., iMC server, iMC plat service) or look for iMC installation directories on the system
    Affected if HPE iMC software is present on the system
  2. Determine the installed iMC platform version
    Locate the iMC version information - typically accessible through the iMC console, management interface, or version file within the installation directory. Compare the version to 7.3
    Affected if The installed iMC version is 7.3 or any version prior to 7.3 (e.g., 7.2, 7.1, etc.)
  3. Verify the iccselectdeviceseries component is exposed
    Check if the /iccselectdeviceseries endpoint is accessible on the iMC web interface (typically port 8080 or 8443). Attempt a curl or similar request to the endpoint to confirm it responds
    Affected if The iccselectdeviceseries endpoint is reachable over the network without authentication
  4. Confirm network accessibility of the iMC management interface
    Test whether the iMC web console port (default 8080/8443) is listening on external interfaces or accessible from untrusted networks
    Affected if The iMC management interface is exposed to untrusted networks and the version is affected

The environment is affected if HPE Intelligent Management Center is installed with version 7.3 or earlier and the iccselectdeviceseries component 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

Upgrade HPE iMC to PLAT 7.3 (E0705P07) or later to patch the vulnerability. If immediate upgrade is not feasible, restrict network access to the iMC management interface using firewall rules or network segmentation.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07) or later

  1. Backup the current HPE Intelligent Management Center installation and database before upgrading
  2. Download iMC PLAT 7.3 (E0705P07) or a later version from the official HPE support website (support.hpe.com)
  3. Follow HPE's official upgrade documentation to install the patched version
  4. After upgrade, verify the iMC services start successfully
  5. Test that the Intelligent Management Center console is accessible and functioning normally
Caveat Review HPE release notes for any configuration or compatibility changes between your current version and 7.3

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

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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