dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2017-5821

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-15
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 Code Execution vulnerability in HPE Intelligent Management Center (iMC) PLAT version 7.3 E0504P04 was found.

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 Code Execution vulnerability in HPE Intelligent Management Center (iMC) PLAT version 7.3 E0504P04 allows unauthenticated remote attackers to execute arbitrary code via unspecified vectors. The CVSS 9.8 indicates network-exploitable with no authentication required and complete impact on confidentiality, integrity, and availability.

MitigationApply HPE's security patch for iMC PLAT 7.3 E0504P04; if no patch available, restrict network access to iMC management interfaces and consider isolating the system until remediation is possible.

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.0/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
    On Windows, check Program Files for HPE or HP Intelligent Management Center folder, or look for the iMC service in Windows Services. On Linux, check common installation directories like /opt/hp/imc or /opt/imc.
    Affected if HPE Intelligent Management Center software is present on the system
  2. Determine iMC PLAT version
    Access the iMC web interface and navigate to Help > About, or check the version file in the installation directory if accessible. The version typically displays as 7.3.x with a build number like E0504P04.
    Affected if The displayed version is 7.3 (any build) or lower than 7.3
  3. Compare version to affected ranges
    Document the exact version number and build (e.g., 7.3, 7.2, 7.1). Compare against the affected range: any version < 7.3 or exactly version 7.3 is vulnerable.
    Affected if Installed version is 7.3 or any version lower than 7.3
  4. Check if iMC management port is exposed
    Verify network accessibility of iMC web interface ports (typically 8080 or 8443). Use netstat or firewall rules to determine if these ports are listening on non-internal network interfaces.
    Affected if The iMC management interface is reachable from network segments beyond the local host

The environment is affected if HPE Intelligent Management Center PLAT version 7.3 or any version lower than 7.3 is installed and the management interface 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

Apply HPE's security patch for iMC PLAT 7.3 E0504P04; if no patch available, restrict network access to iMC management interfaces and consider isolating the system until remediation is possible.

Recommended fix Moderate confidence

Upgrade to a version newer than 7.3 (contact HPE support for the specific fixed release such as 7.3 E0504P07 or later)

  1. 1. Back up the current HPE iMC configuration and database before initiating any upgrade.
  2. 2. Download the fixed version of HPE Intelligent Management Center from the official HPE support portal (support.hpe.com).
  3. 3. Verify the integrity of the downloaded package using checksums provided by HPE.
  4. 4. Schedule a maintenance window to minimize business impact.
  5. 5. Stop all iMC services before proceeding with the upgrade.
  6. 6. Install the upgraded version following HPE's standard installation documentation.
  7. 7. After installation, verify that all services start successfully.
  8. 8. Validate that the iMC web interface is accessible and functional.
Caveat Review HPE release notes for the target version for any configuration or compatibility 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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