CVE-2020-7161
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 reporttaskselect 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 HPE iMC's reporttaskselect component allows unauthenticated attackers to inject and execute arbitrary code via specially crafted EL expressions, leading to complete system compromise with CVSS 9.8 critical severity.
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.
-
Identify HPE iMC installationCheck system for HPE Intelligent Management Center installation by looking for the iMC service or checking common installation directories for imc or hpe imc related foldersAffected if HPE iMC is installed on the system
-
Determine installed iMC versionLocate the version information for the installed HPE iMC instance - typically found in the product's about page, installation directory, or service informationAffected if The installed version is < 7.3 or equals exactly 7.3
-
Verify web interface accessibilityCheck if the HPE iMC web management console is accessible on the network - typically runs on port 8080 or 8443Affected if The web interface is externally accessible or accessible from untrusted networks
-
Test vulnerable endpoint exposureAttempt to access the reporttaskselect component via HTTP request to verify if it responds (e.g., GET request to the reporttaskselect endpoint)Affected if The reporttaskselect endpoint is accessible and responds to requests
A system is affected if HPE Intelligent Management Center is installed with version less than 7.3 or exactly 7.3, and the web-based reporttaskselect component is 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.
dbcve · scoped7.3
Upgrade HPE Intelligent Management Center to PLAT 7.3 (E0705P07) or later to patch the EL injection vulnerability in reporttaskselect.
iMC PLAT 7.3 (E0705P07) or later
- Contact HPE support or visit support.hpe.com to obtain the iMC PLAT 7.3 (E0705P07) or later upgrade package
- Review HPE upgrade documentation for Intelligent Management Center before proceeding
- Plan maintenance window as upgrade may require service interruption
- Execute upgrade following HPE-provided procedures
- Verify successful deployment and test critical iMC functions
- Confirm version post-upgrade shows iMC PLAT 7.3 (E0705P07) or later
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-7161 — 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-7161 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