Intelligent Management CenterApplication · Hp

CVE-2020-7150

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 faultstatchoosefaulttype 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 expression language injection vulnerability in the faultstatchoosefaulttype component of HPE Intelligent Management Center (iMC) allows unauthenticated remote attackers to inject malicious expression language syntax and execute arbitrary code on the underlying system.

MitigationUpgrade HPE iMC to version PLAT 7.3 (E0705P07) or later to patch the expression language injection vulnerability. If immediate patching is not possible, restrict network access to the iMC management interface.

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 installed
    Check for HPE Intelligent Management Center installation by looking for iMC processes running on the system, or check common installation directories such as C:/hp/imc or /opt/hp/imc
    Affected if HPE iMC software is present on the system
  2. Identify installed iMC version
    Locate the iMC version information - typically found in a version file within the installation directory, or check the platform version via the iMC administration console or registry if on Windows
    Affected if The installed version is 7.3 or lower than 7.3 (any version < 7.3 or exactly 7.3)
  3. Verify the faultstatchoosefaulttype component is accessible
    Check if the iMC web interface is exposed and accessible on the network. The vulnerable endpoint is typically at /imc/faultstatchoosefaulttype or similar paths under the iMC web context
    Affected if The iMC web management interface is exposed and reachable
  4. Confirm the EL injection point exists
    Test access to the faultstatchoosefaulttype component by attempting to access the URL endpoint through the iMC web interface
    Affected if The faultstatchoosefaulttype component responds to requests, indicating it is enabled and accessible

A system is affected if HPE Intelligent Management Center version 7.3 or any version below 7.3 is installed and the iMC web interface with the faultstatchoosefaulttype component is 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 version PLAT 7.3 (E0705P07) or later to patch the expression language injection vulnerability. If immediate patching is not possible, restrict network access to the iMC management interface.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07)

  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 before applying the upgrade
  4. 4. Install the iMC PLAT 7.3 (E0705P07) patch following the HPE installation documentation
  5. 5. Restart the iMC services after installation completes
  6. 6. Verify the iMC web interface is accessible and all services are running
  7. 7. Validate that the faultstatchoosefaulttype vulnerability is no longer exploitable

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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