dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2020-7156

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

A remote code execution vulnerability in HPE Intelligent Management Center (iMC) allows unauthenticated attackers to inject malicious expression language syntax through the faultinfo_content parameter, potentially executing arbitrary commands on the affected system.

MitigationUpgrade HPE iMC to PLAT 7.3 (E0705P07) or later. Apply network segmentation and restrict external access to the iMC management interface as an interim measure until patching can be completed.

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. Confirm HPE iMC is present
    Identify whether HPE Intelligent Management Center is installed or running on the system. This may be listed in installed software, running services, or system inventory.
    Affected if HPE iMC is installed on the system
  2. Determine installed iMC version
    Locate and retrieve the version of HPE iMC currently installed. Compare the version number against the affected range: versions less than 7.3 or exactly version 7.3 are vulnerable.
    Affected if Installed version is less than 7.3 or equals exactly 7.3
  3. Identify the vulnerable parameter endpoint
    Locate the web interface or API endpoint that handles the faultinfo_content parameter. This parameter is used for fault information processing and accepts expression language syntax.
    Affected if The faultinfo_content parameter endpoint exists and accepts user-supplied input
  4. Assess network accessibility
    Determine if the iMC management interface is exposed to untrusted networks. Check firewall rules, ACLs, or network segmentation that may restrict access.
    Affected if The iMC interface is reachable from untrusted or external networks without proper access controls

A system is affected if HPE iMC is installed with a version less than 7.3 or exactly 7.3, the faultinfo_content parameter is accessible, and the interface is reachable by unauthenticated attackers.

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. Apply network segmentation and restrict external access to the iMC management interface as an interim measure until patching can be completed.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07) or later

  1. 1. Log into the HPE iMC management console and navigate to the About or System Information section to confirm the current installed version.
  2. 2. Download the iMC PLAT 7.3 (E0705P07) patch or later from the HPE support portal (support.hpe.com) using your HPE account credentials.
  3. 3. Create a complete backup of the iMC database and configuration files before proceeding with the upgrade.
  4. 4. Stop all iMC services through the iMC server control panel or operating system service manager.
  5. 5. Run the iMC PLAT upgrade installer (E0705P07 patch) on the primary server, following the on-screen installation wizard prompts.
  6. 6. After the patch installation completes, start the iMC services and verify all components are running.
  7. 7. Log into the iMC web console and verify the version displays as PLAT 7.3 (E0705P07) or later.
  8. 8. Validate that critical management functions (device discovery, topology, fault management) are operating normally.
Caveat Review HPE release notes for any configuration or feature changes between your current version and 7.3; test thoroughly in a non-production environment before deploying to production

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7156 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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