CVE-2020-7152
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 faultparasset 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 faultparasset expression language injection vulnerability in HPE Intelligent Management Center allows attackers to inject malicious EL expressions that get evaluated by the server's expression language processor, leading to remote code execution with the privileges of the vulnerable service.
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 system for HPE iMC software installation - typically found in Program Files/HPE or similar installation directories, or via system inventory toolsAffected if HPE iMC software is present on the system
-
Determine installed iMC versionLocate the iMC version information - usually accessible via the management console, about page, or version file in the installation directoryAffected if Installed version is lower than 7.3 or equals exactly 7.3
-
Identify if faultparasset feature is accessibleCheck if the faultparasset component is exposed via the iMC web interface or API endpoints - this is the injection point for the expression languageAffected if The faultparasset feature is enabled and accessible to network users
-
Confirm expression language processing is activeVerify that the iMC server's expression language processor is running - this processes the injectable expressionsAffected if Expression language evaluation is enabled on the server
User is affected if HPE iMC is installed with a version lower than 7.3 or equal to 7.3 and the faultparasset feature is accessible, allowing injection of malicious EL expressions for remote code execution.
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 remediate the expression language injection vulnerability.
iMC PLAT 7.3 with patch E0705P07 applied
- Navigate to HPE support.hpe.com and search for HPE Intelligent Management Center
- Locate and download the iMC PLAT 7.3 patch E0705P07
- Apply the patch E0705P07 to your iMC installation following HPE's patch deployment documentation
- Verify the patch was applied successfully by checking the iMC version information
- Restart iMC services if required by the patch installation instructions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7152 — 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-7152 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