CVE-2020-7174
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 soapconfigcontent 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 confidenceAn expression language injection vulnerability in the soapconfigcontent component of HPE Intelligent Management Center allows remote attackers to execute arbitrary code by injecting malicious expressions. The vulnerability stems from unsanitized user input being evaluated as SpEL (Spring Expression Language) or similar expression language, enabling RCE.
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.
-
Verify HPE iMC is installedCheck for HPE Intelligent Management Center installation by looking for the iMC application directory, service, or management console access. Common installation paths include C:\hp\iMC or /opt/hp/imc. On Windows, check Services for 'HPE iMC' or 'Intelligent Management Center' service.Affected if HPE iMC software is present on the system
-
Determine installed iMC versionAccess the iMC management console login page, or check the About/Version information within the application. The version is typically displayed on the login page footer or in the admin section. If command-line access is available, check the installation directory for version files.Affected if The installed version is 7.3 or any version below 7.3 (versions < 7.3 or = 7.3)
-
Confirm soapconfigcontent component is accessibleThe vulnerability exists in the soapconfigcontent component. Check if this web service endpoint is exposed by attempting to access the iMC web interface on typical ports (8080, 8443). The soapconfigcontent is typically accessible at /soapconfigcontent or similar endpoints under the iMC web application path.Affected if The iMC web management interface and soapconfigcontent component are reachable from the network
If HPE Intelligent Management Center version 7.3 or below is installed AND the soapconfigcontent component is network-accessible, the environment is affected by this CVE.
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 to HPE iMC PLAT 7.3 (E0705P07) or later. If immediate patching is not feasible, restrict network access to the iMC management interface to trusted sources only.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7174 — 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-7174 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