Intelligent Management CenterApplication · Hp

CVE-2020-7195

HIGH · 8.8 CVSS v3.1 Published 2020-10-19
Fix available
A fix is available. Upgrade to 7.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 iccselectrules 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 iccselectrules component that allows remote attackers to execute arbitrary code via specially crafted expressions. This is a critical injection flaw that bypasses normal input sanitization by injecting malicious expression language syntax.

MitigationUpgrade HPE iMC to PLAT 7.3 (E0705P07) or later. If immediate patching is not possible, restrict network access to the iMC management interfaces to trusted IPs only.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 iMC is installed
    Check for HPE Intelligent Management Center installation by looking for the iMC service or process. On Windows, check Services for 'HP Intelligent Management Center' or look in Program Files for the iMC installation directory. On Linux, check for /opt/imc or similar installation paths.
    Affected if HPE Intelligent Management Center is installed on the system
  2. Determine the installed iMC version
    Locate the version file or check the iMC management console for the PLAT version number. On Windows, the version is often found in the installation directory or can be retrieved via the iMC admin web interface under 'About' or 'System Information'.
    Affected if The installed version is lower than 7.3 or equals exactly 7.3
  3. Check if the iccselectrules component is exposed
    Verify that the iMC web interface is accessible and the iccselectrules endpoint is available. This typically involves checking if port 8080 or 8443 (iMC web console ports) are open and responding.
    Affected if The iMC web interface with the iccselectrules component is accessible from the network
  4. Confirm the vulnerable endpoint is reachable
    Attempt to access the iccselectrules URL pattern (typically /imc/iccselectrules or similar paths under the iMC web context) via HTTP/HTTPS to confirm the component responds. This can be done with a simple curl or browser request to the management interface.
    Affected if The iccselectrules endpoint returns a valid response, indicating the vulnerable component is active

A system is affected if HPE Intelligent Management Center is installed with version 7.3 or below and the iccselectrules web component is accessible on the network.

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.

From vendor data
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 not possible, restrict network access to the iMC management interfaces to trusted IPs only.

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