Intelligent Management CenterApplication · Hp

CVE-2020-7168

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

HPE Intelligent Management Center contains an expression language injection vulnerability in the selectusergroup component that allows unauthenticated attackers to inject malicious expressions and achieve remote code execution.

MitigationUpgrade HPE iMC to PLAT 7.3 (E0705P07) or later to patch the expression language injection vulnerability.

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. Verify HPE Intelligent Management Center is installed
    Check for iMC installation directories (commonly at C:\hp\imc or /opt/hp/imc) or search for imc-related services running on the system
    Affected if HPE iMC is present on the system
  2. Determine installed iMC version
    Check the version file in the iMC installation directory, typically found in version.properties or about.html within the imc folder, or query the iMC service if accessible
    Affected if The version is less than 7.3 or exactly 7.3
  3. Identify selectusergroup component accessibility
    Check if the /selectusergroup endpoint is exposed on the iMC web interface (default port 8080 or 8443). Attempt to access the URL pattern: http(s)://<server>:<port>/selectusergroup
    Affected if The selectusergroup endpoint responds without authentication
  4. Confirm vulnerability condition
    Cross-reference: if version is < 7.3 or = 7.3 AND selectusergroup endpoint is reachable over the network, the system is vulnerable to unauthenticated expression language injection
    Affected if Both version is within affected range AND selectusergroup component is network-accessible

A system is affected if HPE Intelligent Management Center version 7.3 or below is installed and the selectusergroup web component is exposed and 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 to patch the expression language injection vulnerability.

Recommended fix Moderate confidence

iMC PLAT 7.3 (E0705P07) or later

  1. 1. Back up the current HPE Intelligent Management Center configuration and database
  2. 2. Download the fixed version iMC PLAT 7.3 (E0705P07) or later from the HPE support portal (support.hpe.com)
  3. 3. Stop all iMC services before applying the upgrade
  4. 4. Install the iMC PLAT 7.3 (E0705P07) patch or upgrade to the latest stable version
  5. 5. Restart iMC services and verify the application is functioning correctly
  6. 6. Confirm the selectusergroup expression language injection vulnerability is resolved by testing or consulting vendor documentation
Caveat Review HPE release notes for any configuration or compatibility changes between your current version and 7.3

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,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 $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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