CVE-2020-7192
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 devicethresholdconfig 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 vulnerability in HPE iMC's devicethresholdconfig component allows remote attackers to inject malicious expression language code that gets interpreted and executed by the server, leading to remote code execution. The vulnerability stems from insufficient input validation of user-supplied data in the devicethresholdconfig expression evaluation context.
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.
-
Identify installed HPE iMC versionAccess the iMC management console or check the product version through the About/Help section in the web interface, or retrieve it from the system's installed programs listAffected if The version is lower than 7.3 or exactly 7.3
-
Locate the devicethresholdconfig componentCheck if the /devicethresholdconfig endpoint is accessible on the iMC web server (typically ports 8080, 8443, or 443)Affected if The devicethresholdconfig endpoint is reachable and responds to requests
-
Verify network exposure of iMC interfaceDetermine if the iMC management interface is directly accessible from untrusted networks (internet-facing or insufficiently segmented)Affected if The iMC web console is exposed to unauthorized or untrusted network segments
-
Check for expression evaluation functionalityReview the devicethresholdconfig feature in the iMC console to confirm it accepts and evaluates expression language inputAffected if The feature that processes expressions in devicethresholdconfig is enabled and functional
-
Confirm iMC PLAT patch levelIf version 7.3 is installed, verify the specific patch version (look for E0705P07 or later in the build/patch information)Affected if Running iMC 7.3 without the E0705P07 patch applied
You are affected if HPE iMC is installed at version 7.3 or any version below 7.3, and the devicethresholdconfig component is accessible on your 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.
From vendor data7.3
Upgrade HPE Intelligent Management Center to iMC PLAT 7.3 (E0705P07) or later to patch the expression language injection vulnerability. If immediate patching is not feasible, restrict network access to the iMC management interface and implement network segmentation to limit exposure.
- Consultation4.0 h
- Implementation4.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7192 — 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-7192 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