dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2020-24648

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 accessmgrservlet classname deserialization of untrusted data 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 confidence

A deserialization vulnerability in the accessmgrservlet class of HPE Intelligent Management Center (iMC) allows remote attackers to execute arbitrary code by sending crafted serialized Java objects. The vulnerability stems from insecure deserialization of untrusted data without proper validation, enabling complete system compromise.

MitigationUpgrade HPE Intelligent Management Center to version PLAT 7.3 (E0705P07) or later. If immediate patching is not possible, network segmentation and restricting access to the affected servlet should be implemented as interim controls.

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. Verify HPE iMC is installed
    Check for HPE Intelligent Management Center installation by looking for the product directory, typically under C:\hp\iMC or /opt/hp/imc, or check Windows Services for 'HPE iMC' or 'Intelligent Management Center' services
    Affected if The product is not installed - not affected. If installed, continue to version check.
  2. Determine installed iMC version
    Locate the version file or check the platform.properties/version.xml in the iMC installation directory, or access the iMC web console and check the About/Version information page
    Affected if If version is 7.3 (any patch level) or lower than 7.3, the system is in the affected version range.
  3. Confirm accessmgrservlet exposure
    Check if the web interface is accessible by attempting to reach http(s)://<server>:8080/accessmgrservlet or looking for the accessmgr servlet configuration in the deployment descriptors (web.xml) within the iMC application server
    Affected if If the servlet is deployed and accessible via the web interface, the attack surface exists.
  4. Check network accessibility of the servlet
    Review firewall rules and network configuration to determine if the iMC web console port (default 8080 or 8443) is exposed to untrusted networks or the internet
    Affected if If the servlet port is accessible from untrusted networks, the vulnerability is remotely exploitable.

A user is affected if HPE Intelligent Management Center version 7.3 or lower is installed and the accessmgrservlet 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 Intelligent Management Center to version PLAT 7.3 (E0705P07) or later. If immediate patching is not possible, network segmentation and restricting access to the affected servlet should be implemented as interim controls.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07) or later

  1. 1. Back up the HPE Intelligent Management Center configuration and database
  2. 2. Navigate to the HPE support portal (support.hpe.com) and locate HPE Intelligent Management Center
  3. 3. Download iMC PLAT 7.3 (E0705P07) or a later stable release
  4. 4. Stop the iMC services before applying the upgrade
  5. 5. Run the installer to upgrade to the fixed version
  6. 6. Start the iMC services and verify the application is operational
  7. 7. Confirm the accessmgrservlet vulnerability is remediated
Caveat Review HPE iMC 7.3 release notes for any configuration or feature changes before upgrading

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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-24648 — 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-24648 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