CVE-2020-7141
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 adddevicetoview 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 confidenceExpression language injection vulnerability in the 'adddevicetoview' functionality of HPE Intelligent Management Center allows unauthenticated attackers to inject and execute arbitrary code via crafted EL expressions, leading to complete system compromise.
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 Intelligent Management Center is installedCheck for iMC installation by looking for the installation directory (commonly at C:\hp\iMC or /opt/hp/imc) or check Windows Services for 'HP Intelligent Management Center' serviceAffected if iMC software is present on the system
-
Determine installed iMC platform versionLocate the version file in the iMC installation directory, typically in a version.properties or similar file, or check the iMC web UI login page footer for the build versionAffected if The installed version is lower than 7.3 or equals exactly 7.3
-
Check if web management interface is exposedVerify the iMC web console is accessible by attempting to reach the login page (default ports 8080 or 8443), and check if the 'adddevicetoview' endpoint respondsAffected if The web interface is reachable from network locations
-
Verify network accessibility of iMC servicesUse netstat or similar tool to confirm listening ports for iMC (http-alt 8080, https-alt 8443) and determine if these ports are bound to 0.0.0.0 or an exposed network interfaceAffected if iMC management ports are exposed to untrusted networks (not localhost or internal VLAN only)
If HPE iMC is installed and the installed version is 7.3 or below (any build prior to E0705P07) with the web interface network-accessible, the environment is vulnerable to unauthenticated EL injection via the adddevicetoview function.
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 version 7.3 (E0705P07) or later. If immediate patching is not possible, restrict network access to the iMC management interfaces.
iMC PLAT 7.3 (E0705P07) or later
- 1. Check current HPE iMC version by accessing the iMC console or checking system information
- 2. Create a complete backup of the iMC database and configuration
- 3. Download the fixed version iMC PLAT 7.3 (E0705P07) or later from the HPE support portal (support.hpe.com)
- 4. Stop all iMC services before applying the upgrade
- 5. Install the iMC PLAT 7.3 (E0705P07) patch or upgrade following HPE's official upgrade documentation
- 6. Restart iMC services after installation completes
- 7. Verify the version has been updated to 7.3 (E0705P07) or later
- 8. Test critical functionality to ensure the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7141 — 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-7141 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