dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2020-24647

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 remote accessmgrservlet classname input validation 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

HPE Intelligent Management Center (iMC) contains a remote code execution vulnerability in the accessmgrservlet due to insufficient input validation on the classname parameter. This allows unauthenticated remote attackers to execute arbitrary code on the affected system by sending specially crafted requests.

MitigationUpgrade HPE iMC to version PLAT 7.3 (E0705P07) or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation and restricting access to the iMC management interfaces.

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. Identify HPE iMC installed version
    Locate the iMC installation directory and check version information in the platform configuration files, typically found in the iMC installation folder under plat/conf directory, or use the iMC client to view the platform version information
    Affected if The installed version is 7.3 or any version lower than 7.3 (versions < 7.3 or = 7.3)
  2. Verify accessmgrservlet is present
    Check for the existence of the accessmgr servlet in the deployed web applications. This servlet is typically found in the iMC web deployment under the management or platform application directory
    Affected if The servlet file accessmgrservlet is present and deployed in the iMC web application directory
  3. Confirm the vulnerable endpoint is network accessible
    Test if the accessmgrservlet endpoint is reachable from the network by attempting to access it via HTTP/HTTPS on the iMC management port (default 8080 or 8443)
    Affected if The endpoint is accessible over the network without authentication requirements
  4. Check if remote management interface is enabled
    Verify that the iMC web-based management console is enabled and listening on configured ports by reviewing the iMC server configuration settings
    Affected if The management interface is enabled and bound to a network-accessible IP address

A system is affected if HPE Intelligent Management Center version 7.3 or any version below 7.3 is installed AND the accessmgrservlet is exposed on the network.

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 version PLAT 7.3 (E0705P07) or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation and restricting access to the iMC management interfaces.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07)

  1. 1. Back up the current HPE Intelligent Management Center configuration and database
  2. 2. Download iMC PLAT 7.3 (E0705P07) from the HPE support portal (support.hpe.com)
  3. 3. Stop all iMC services before initiating the upgrade
  4. 4. Run the iMC PLAT 7.3 (E0705P07) installer on the iMC server
  5. 5. Follow the on-screen upgrade wizard instructions, selecting the upgrade option
  6. 6. After upgrade completes, verify all iMC services start successfully
  7. 7. Validate that the accessmgrservlet vulnerability is no longer exploitable
Caveat Review HPE iMC 7.3 release notes for any configuration or feature changes from prior versions 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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