dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2020-24652

CRITICAL · 9.8 CVSS v3.1 Published 2020-10-19
Fix available
A fix is available. Upgrade to 7.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A addvsiinterfaceinfo 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 confidence

Expression language injection vulnerability in HPE Intelligent Management Center's addvsiinterfaceinfo function allows remote attackers to inject and execute malicious expression language statements, leading to arbitrary code execution on the affected system.

MitigationUpgrade HPE iMC to PLAT 7.3 (E0705P07) or later. If immediate upgrade is not feasible, restrict network access to the iMC management interfaces and implement additional monitoring for suspicious patterns.

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
Intelligent Management CenterApplication
Affected:< 7.3= 7.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm HPE iMC is installed
    Check for HPE Intelligent Management Center installation directory or running service. Common paths include C:\hp\imc or typical Windows program files. Also check Windows Services for 'HPE iMC' or 'Intelligent Management Center' service.
    Affected if HPE Intelligent Management Center is found running on the system
  2. Determine installed iMC version
    Locate the iMC version information, typically in a version file, about dialog, or service properties. Common locations include the installation directory or registry keys under HKLM\Software\Hewlett-Packard\iMC.
    Affected if Installed version is less than 7.3 or exactly equals 7.3
  3. Identify if addvsiinterfaceinfo function is exposed
    Check if the iMC web interface or API endpoints are accessible. The addvsiinterfaceinfo function is part of the iMC service. Verify network accessibility of iMC management ports (default 8080, 8443).
    Affected if iMC management interface is network-accessible and the vulnerable function is reachable
  4. Review iMC logs for exploitation indicators
    Examine iMC server logs in the installation's logs directory for suspicious expression language patterns, unusual queries, or unexpected code execution attempts targeting the addvsiinterfaceinfo function.
    Affected if Logs show suspicious EL injection patterns or unauthorized access attempts to the vulnerable function

A system is affected if HPE Intelligent Management Center is installed with version 7.3 or below and the addvsiinterfaceinfo function is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.3 or later
Fixed in 7.3
Interim mitigation

Upgrade HPE iMC to PLAT 7.3 (E0705P07) or later. If immediate upgrade is not feasible, restrict network access to the iMC management interfaces and implement additional monitoring for suspicious patterns.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07) or later

  1. 1. Back up the current HPE Intelligent Management Center configuration and database
  2. 2. Download iMC PLAT 7.3 (E0705P07) or later from the HPE support portal (support.hpe.com)
  3. 3. Review HPE iMC upgrade documentation for migration requirements
  4. 4. Apply the upgrade to all iMC components following HPE's standard upgrade procedure
  5. 5. Verify the upgrade was successful by checking the iMC version
  6. 6. Test critical management functions to ensure normal operation
Caveat Standard iMC upgrade considerations apply - review migration docs for database and configuration compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-24652 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-24652 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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