CVE-2020-7165
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 · uneditedA iccselectcommand 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 confidenceA critical expression language injection vulnerability in the iccselectcommand component of HPE Intelligent Management Center (iMC) allows unauthenticated attackers to inject malicious expressions that execute arbitrary code on the target system. This class of vulnerability occurs when user-supplied input is passed to an expression parser (such as OGNL or similar) without proper sanitization, enabling remote code execution.
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< 7.3= 7.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify HPE iMC installation existsCheck for the presence of HPE Intelligent Management Center installation directory (typically at C:\hp\iMC or C:\Program Files\HP\iMC) or look for the iMC service running on the system using 'services.msc' or 'sc query' commands.Affected if HPE iMC software is installed on the system
-
Determine installed iMC versionLocate the version file in the iMC installation directory, typically in a version.ini, about.jar, or check the iMC PLAT version through the application web interface under Help > About, or inspect the iMC_PLAT installation folder for version manifests.Affected if The installed version is 7.3 or any version lower than 7.3 (e.g., 7.2, 7.1, 7.0)
-
Confirm iccselectcommand component is exposedIdentify if the iccselectcommand endpoint is accessible by checking network listeners on the iMC server ports (typically 8080, 8443 for web interface). Review server configuration files (server.xml, web.xml) in the iMC deployment for servlet mappings to iccselectcommand.Affected if The HPE iMC web management interface is listening on accessible network ports and the iccselectcommand servlet is mapped and enabled
-
Check network exposure of management interfaceReview firewall rules and network configuration to determine if the iMC management ports (HTTP/HTTPS) are bound to external interfaces or only to localhost/internal network using 'netstat -an | findstr 8080' or similar port inspection.Affected if The iMC management interface is reachable from untrusted networks (not restricted to localhost or trusted internal subnets)
The system is affected if HPE Intelligent Management Center version 7.3 or below is installed AND the iccselectcommand component is accessible via the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.3
Upgrade HPE iMC to PLAT 7.3 (E0705P07) or later to obtain the patched version. If immediate patching is not possible, restrict network access to iMC management interfaces and implement WAF rules to detect and block expression language injection patterns.
iMC PLAT 7.3 (E0705P07)
- 1. Back up the HPE Intelligent Management Center database and configuration files.
- 2. Download iMC PLAT 7.3 (E0705P07) or later from the HPE support portal (support.hpe.com).
- 3. Stop the iMC services on the affected server.
- 4. Apply the iMC PLAT 7.3 (E0705P07) upgrade following the HPE installation/upgrade guide.
- 5. After installation, restart the iMC services.
- 6. Verify the iMC web interface is accessible and all services are running normally.
- 7. Confirm the version by checking About or the version information in the iMC console.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7165 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-7165 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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