CVE-2020-7190
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 deviceselect 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 in the deviceselect component of HPE Intelligent Management Center allows unauthenticated remote attackers to execute arbitrary code by injecting malicious expressions, prior to version 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.
-
Check HPE iMC version via web interfaceLog into the HPE iMC web console and navigate to the About or System Information page to view the platform version. Look for a version string that may display as PLAT x.x or similar.Affected if The displayed version is < 7.3 or equals exactly 7.3 (prior to E0705P07)
-
Identify the specific PLAT build numberOn the About page, locate the full version/build identifier. HPE iMC versions are often labeled as PLAT X.X (E0705PXX) where the suffix indicates the specific patch level.Affected if The build number is earlier than E0705P07, or the version shows 7.3 without the E0705P07 suffix
-
Verify deviceselect component accessibilityAttempt to access the deviceselect endpoint via HTTP/HTTPS at your iMC server URL (commonly /deviceselect/ or similar path under the iMC web root). A reachable or responsive endpoint indicates the component is exposed.Affected if The deviceselect component is accessible over the network without authentication
-
Cross-reference version from config filesCheck installation directory configuration files for version metadata. Common locations include files named version.properties, about.xml, or similar in the iMC installation directory.Affected if The version found in config files confirms < 7.3 or = 7.3
If the installed HPE iMC version is earlier than PLAT 7.3 (E0705P07) or exactly version 7.3, and the deviceselect component is network-accessible, the environment is vulnerable to CVE-2020-7190.
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 HPE iMC to version PLAT 7.3 (E0705P07) or later to remediate the vulnerability. If immediate patching is not possible, restrict network access to the iMC management interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7190 — 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-7190 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