CVE-2020-7153
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 iccselectdevtype 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 Intelligent Management Center's 'iccselectdevtype' component allows unauthenticated remote attackers to inject malicious expression language syntax and execute arbitrary OS commands on the affected system.
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 versionAccess the HPE Intelligent Management Center web console and navigate to the About or Version information page, or check version files in the iMC installation directory if you have server accessAffected if The installed version is 7.3 or any version below 7.3 (the affected range)
-
Locate the iccselectdevtype endpointAttempt to access the vulnerable component via HTTP/HTTPS at the path /icc/iccselectdevtype on your iMC server (e.g., http://your-imc-server:8080/icc/iccselectdevtype or https://your-imc-server:8443/icc/iccselectdevtype)Affected if The endpoint returns any HTTP response (even an error page), indicating the component is present and exposed
-
Verify network exposure of iMC web interfaceReview firewall rules, ACLs, or network boundary devices to determine if the iMC management interface (typically ports 8080 or 8443) is reachable from untrusted networks or the internetAffected if The iMC web interface is accessible from networks outside your trusted administrative zone
-
Confirm authentication requirements for the iccselectdevtype componentSend a request to the iccselectdevtype endpoint without providing any authentication credentials and observe whether the component processes the request or returns an authentication challengeAffected if The component processes requests without requiring authentication, meaning it is vulnerable to unauthenticated exploitation
Your environment is affected if HPE iMC version is 7.3 or lower and the iccselectdevtype component is exposed to network attackers without authentication controls.
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. If immediate patching is not possible, restrict network access to the iMC management interface and implement WAF rules to detect and block expression language injection attempts.
iMC PLAT 7.3 (E0705P07) or later
- 1. Obtain HPE Intelligent Management Center PLAT 7.3 (E0705P07) or later from support.hpe.com
- 2. Review the HPE iMC upgrade guide for your current version to understand prerequisites
- 3. Create a complete backup of the iMC database and configuration files
- 4. Stop all HPE iMC services on the server
- 5. Install iMC PLAT 7.3 (E0705P07) using the HPE installation documentation
- 6. After installation, verify the version shows 7.3 (E0705P07) or later in the iMC console or about page
- 7. Start iMC services and confirm the platform operates normally
- 8. Validate that the iccselectdevtype functionality works correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7153 — 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-7153 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