dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2020-7143

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 faultdevparasset 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 critical expression language injection vulnerability in the faultdevparasset component of HPE Intelligent Management Center (iMC) allows remote unauthenticated attackers to execute arbitrary operating system commands by injecting malicious expressions. This network-exploitable RCE flaw affects all versions prior to iMC PLAT 7.3 (E0705P07), granting attackers complete system compromise.

MitigationUpgrade HPE iMC to PLAT 7.3 (E0705P07) or later. If immediate patching is infeasible, implement network segmentation and restrict access to iMC management interfaces from untrusted networks.

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 HPE iMC installation
    Check for HPE Intelligent Management Center software on the system by searching for iMC-related processes, services, or installed applications. On Windows, check Program Files for HPE or iMC folders; on Linux, check /opt or standard application directories.
    Affected if HPE iMC software is found running on the system
  2. Determine iMC PLAT version
    Locate the iMC platform version information. This is typically accessible through the iMC management console, about section, or version files within the iMC installation directory.
    Affected if The installed iMC PLAT version is less than 7.3 or equals exactly 7.3 (prior to E0705P07)
  3. Verify faultdevparasset component exposure
    Check if the faultdevparasset web component is accessible. This is typically exposed via the iMC web interface on ports 8080, 8443, or similar management ports. Attempt to access the component endpoint through the network.
    Affected if The faultdevparasset endpoint is reachable over the network without authentication
  4. Assess network accessibility of iMC management interface
    Determine if the iMC management web interface (ports 8080/tcp, 8443/tcp, or configured HTTPS port) is exposed to untrusted networks. Check firewall rules and network segmentation around the iMC server.
    Affected if The iMC management interface is accessible from untrusted or external networks without proper network filtering

A user is affected if HPE iMC is installed with a version prior to PLAT 7.3 (E0705P07) and the faultdevparasset 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. If immediate patching is infeasible, implement network segmentation and restrict access to iMC management interfaces from untrusted networks.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07) or later

  1. Download the iMC PLAT 7.3 (E0705P07) patch or later from the HPE support portal (support.hpe.com)
  2. Review the HPE iMC upgrade guide and release notes for prerequisites
  3. Ensure all system prerequisites are met (database backup, system requirements, etc.)
  4. Create a complete backup of the current iMC database and configuration
  5. Stop all iMC services before applying the upgrade
  6. Install iMC PLAT 7.3 (E0705P07) patch following the documented upgrade procedure
  7. Restart iMC services after the patch is successfully applied
  8. Verify the iMC platform is operational and the web interface is accessible
Caveat Review release notes for any configuration changes or deprecations between your current version and 7.3; test in non-production environment first

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

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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