Intelligent Management CenterApplication · Hp

CVE-2020-24629

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 urlaccesscontroller authentication bypass 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 remote authentication bypass vulnerability in HPE Intelligent Management Center's URL access controller allows unauthenticated remote attackers to bypass authentication mechanisms and gain unauthorized access to the platform. This is a critical flaw in the access control layer that can be exploited without credentials.

MitigationUpgrade HPE iMC to PLAT version 7.3 (E0705P07) or later to remediate this vulnerability. If immediate upgrade is not feasible, implement network segmentation and restrict access to the iMC management interfaces to trusted networks only.

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. Check HPE iMC platform version
    Locate the iMC installation directory and find the version information file, or access the iMC web console and look for the version displayed in the About or System Information page
    Affected if The installed version is any version below 7.3 or exactly 7.3 (prior to E0705P07 update)
  2. Verify iMC web interface accessibility
    Determine if the HPE iMC web console is accessible over network by attempting to reach the management URL (typically port 8080 or 8443) from an untrusted network
    Affected if The iMC web interface is exposed to untrusted networks and the installed version falls within the affected range
  3. Confirm URL access controller is active
    Check if the iMC platform services are running and the URL access controller module is loaded - this is typically a core authentication component that is enabled by default when iMC is operational
    Affected if The iMC services are running and the URL access controller component is active (which is the default state)
  4. Review authentication configuration
    Access the iMC administrative console and navigate to the access control or security configuration section to examine the URL access controller settings
    Affected if The URL access controller is configured with default or weak settings and the version is within the affected range

You are affected if HPE Intelligent Management Center is running and the installed version is either below 7.3 or exactly 7.3 (prior to the E0705P07 patch), with the web management interface accessible over 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 PLAT version 7.3 (E0705P07) or later to remediate this vulnerability. If immediate upgrade is not feasible, implement network segmentation and restrict access to the iMC management interfaces to trusted networks only.

Recommended fix High confidence

iMC PLAT 7.3 (E0705P07)

  1. Download iMC PLAT 7.3 (E0705P07) or later from the HPE Support Center (support.hpe.com)
  2. Ensure you have a complete backup of your current iMC configuration and database
  3. Stop the iMC services before applying the upgrade
  4. Apply the iMC PLAT 7.3 (E0705P07) patch or upgrade package
  5. Verify the installation completed successfully
  6. Start the iMC services and confirm they are running
  7. Log in to the iMC console and verify the version shows 7.3 (E0705P07) or later
  8. Validate that core functionality (authentication, device management) is working correctly

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

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-24629 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