Intelligent Management CenterApplication · Hp

CVE-2020-7147

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 deployselectbootrom 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 · high confidence

An expression language injection vulnerability in the deployselectbootrom component of HPE Intelligent Management Center allows remote attackers to inject and execute arbitrary code via crafted EL syntax. The flaw is network-exploitable with low complexity and no authentication required, enabling complete system compromise.

MitigationUpgrade to HPE iMC PLAT 7.3 (E0705P07) or later. Prior to patching, restrict network access to the iMC management interface and monitor for indicators of compromise.

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. Check HPE iMC version
    Access the iMC management console or check the installation directory for version information. Typically found in the product UI under 'About' or in installation logs/config files.
    Affected if Version is earlier than 7.3 E0705P07 (i.e., < 7.3 or = 7.3 base release)
  2. Verify deployselectbootrom component status
    Check if the deployselectbootrom component is installed and enabled in the iMC platform. This is typically visible in the iMC console under component management or deployment features.
    Affected if The component is installed and accessible via the web interface
  3. Confirm network exposure of iMC management interface
    Determine if the iMC management interface is directly accessible from untrusted networks. Check firewall rules, reverse proxy configurations, or ACLs controlling access to the iMC web ports (typically 8080, 8443, or 443).
    Affected if The management interface is exposed to the internet or untrusted internal networks without proper access controls
  4. Review iMC server for indicators of compromise
    Examine iMC server logs, especially under the deployselectbootrom component path, for suspicious requests containing EL syntax patterns like '${' '}'. Check for unexpected files, new user accounts, or reverse shells.
    Affected if Logs show suspicious EL injection patterns or evidence of unauthorized code execution

You are affected if HPE iMC version is earlier than 7.3 E0705P07 AND the deployselectbootrom component is accessible from your network.

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 to HPE iMC PLAT 7.3 (E0705P07) or later. Prior to patching, restrict network access to the iMC management interface and monitor for indicators of compromise.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07) or later

  1. 1. Back up the current HPE Intelligent Management Center configuration and database.
  2. 2. Download iMC PLAT 7.3 (E0705P07) or later from the HPE support portal (support.hpe.com).
  3. 3. Stop the iMC services on the affected server.
  4. 4. Apply the iMC PLAT 7.3 (E0705P07) upgrade following the HPE upgrade documentation.
  5. 5. Restart the iMC services after the upgrade completes.
  6. 6. Verify the iMC web interface is accessible and all services are running.
  7. 7. Validate that the expression language injection vulnerability is no longer exploitable.
Caveat Review HPE release notes for iMC PLAT 7.3 for any compatibility or configuration changes 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
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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