Intelligent Management CenterApplication · Hp

CVE-2020-7171

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

Expression language injection vulnerability in HPE Intelligent Management Center (iMC) guidatadetail component allows remote code execution in versions prior to iMC PLAT 7.3 (E0705P07). The flaw enables attackers to inject malicious expressions that are evaluated by the application's EL processor, leading to full system compromise.

MitigationApply HPE iMC PLAT 7.3 (E0705P07) or later patch to remediate the vulnerability. Upgrade from any earlier version of iMC to the patched release.

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 version via web interface
    Log into the HPE iMC web console and navigate to the About or System Information page, typically found under Administration or Help menus, to view the exact build version including the patch level (E0705P07).
    Affected if The displayed version shows anything earlier than PLAT 7.3 (E0705P07) or shows version 7.3 without the E0705P07 patch identifier.
  2. Check iMC platform version on the server
    On the server hosting iMC, locate the platform version file or check the installation directory for version metadata. Common locations include the iMC installation folder or configuration files that store the build number.
    Affected if The version file or metadata indicates a build prior to E0705P07 or shows version 7.3 without that specific patch level.
  3. Identify if guidatadetail component is exposed
    Check the iMC web application configuration or web.xml to determine if the guidatadetail servlet/endpoint is publicly accessible. This component handles GUI data display and is the injection point.
    Affected if The guidatadetail component is enabled and accessible without authentication or from untrusted network locations.
  4. Review access logs for EL injection patterns
    Examine iMC web access logs (typically in the iMC/logs directory) for unusual query patterns containing dollar signs and brackets such as ${, #{, or common execution patterns like Runtime.getRuntime().
    Affected if Logs contain requests with expression language syntax targeting the guidatadetail endpoint that suggest exploitation attempts.

A user is affected if their HPE iMC installation shows a version lower than PLAT 7.3 (E0705P07) or displays version 7.3 without the specific E0705P07 patch applied.

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

Apply HPE iMC PLAT 7.3 (E0705P07) or later patch to remediate the vulnerability. Upgrade from any earlier version of iMC to the patched release.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07)

  1. Backup the HPE iMC database and configuration before upgrading
  2. Download iMC PLAT 7.3 (E0705P07) from support.hpe.com
  3. Upgrade HPE Intelligent Management Center to version PLAT 7.3 (E0705P07)
  4. Verify the upgrade was successful and restart all iMC services

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-7171 — 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-7171 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