CVE-2020-7175
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 iccselectdymicparam 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 confidenceExpression language injection in the iccselectdymicparam component of HPE Intelligent Management Center allows remote code execution by injecting malicious EL expressions. The vulnerability affects versions prior to iMC PLAT 7.3 (E0705P07).
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm HPE iMC is installedCheck for the presence of HPE Intelligent Management Center installation directory (typically C:\hp\iMC or C:\Program Files\HP\iMC) or look for the 'hpimcd' or 'iMC' service running via 'services.msc' or 'sc query'.Affected if The product is not installed or the service is not found.
-
Determine installed iMC platform versionNavigate to the iMC installation directory and locate the version file (commonly version.ini, about.html, or check the service properties). Alternatively, access the iMC web console login page and check the version displayed, or run: 'reg query "HKLM\SOFTWARE\Hewlett-Packard\iMC" /v Version' if registry keys exist.Affected if Unable to retrieve version information.
-
Compare version against affected rangeThe affected versions are any release prior to iMC PLAT 7.3 (E0705P07) AND version 7.3 itself (prior to patch E0705P07). If the version is 7.3, verify whether patch E0705P07 has been applied. If version is below 7.3, it is affected.Affected if Installed version is less than 7.3, or is exactly 7.3 without patch E0705P07 applied.
-
Verify iccdynamicparam component exposureThe vulnerability exists in the 'iccdynamicparam' web component. Check if the iMC web interface is accessible externally (port 8080 or 8443 typically). Attempt to access the path /imc/iccdynamicparam or verify via network scanning that the iMC console is exposed.Affected if The iMC web console and specifically the iccdynamicparam endpoint are accessible from the network.
A system is affected if HPE iMC is installed with a version less than 7.3, or exactly version 7.3 without the E0705P07 patch, and the web console (containing the vulnerable iccdynamicparam component) is network-accessible.
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.
From vendor data7.3
Upgrade to HPE iMC PLAT 7.3 (E0705P07) or later to remediate this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2020-7175 — 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-7175 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