dbcve.org
Intelligent Management Center PlatApplication · Hp

CVE-2017-5791

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
The doFilter method in UrlAccessController in HPE Intelligent Management Center (iMC) PLAT 7.2 E0403P06 allows remote bypass of authentication via unspecified strings in a URI.

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

Authentication bypass vulnerability in HPE iMC PLAT's UrlAccessController doFilter method allows remote attackers to bypass authentication by including specific strings in URI requests. The vulnerability stems from improper validation of authentication credentials in the URL filtering mechanism.

MitigationApply the HPE iMC PLAT 7.2 E0403P06 patch or upgrade to a patched version. Restrict network access to the iMC management interface to trusted IPs until patch is applied.

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 Center PlatApplication
Affected:= 7.2

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. Confirm HPE iMC PLAT is installed
    Check for HPE Intelligent Management Center installation by looking for the iMC service processes or installation directory. Common paths: C:/Program Files/Hewlett Packard Enterprise/iMC or /opt/hpe/imc
    Affected if The product is not installed or is a different product entirely
  2. Identify installed iMC PLAT version
    Check the version of HPE iMC PLAT installed. Navigate to the iMC installation directory and look for version information in about dialog, version.txt, or check the iMC web interface login page which often displays version information
    Affected if Version is 7.2 (exact match to affected version)
  3. Verify UrlAccessController component is in use
    Examine the iMC web application configuration. The vulnerability is in the UrlAccessController doFilter method which handles URL-based access control. Check if the /ui/ or /imc/ web paths are accessible and check application logs for UrlAccessController activity
    Affected if The URL filtering/UrlAccessController component is active and handling requests
  4. Check network exposure of iMC management interface
    Determine if the HPE iMC web console (typically ports 8080 or 8443) is accessible from untrusted networks. Use netstat or firewall rules to identify binding addresses: netstat -an | grep -E '8080|8443' or review firewall configuration
    Affected if iMC management interface is bound to 0.0.0.0 or exposed to untrusted networks rather than localhost/internal subnets only

You are affected if HPE iMC PLAT version 7.2 is installed AND the management interface is network-accessible, as the UrlAccessController authentication bypass can be exploited remotely.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the HPE iMC PLAT 7.2 E0403P06 patch or upgrade to a patched version. Restrict network access to the iMC management interface to trusted IPs until patch is applied.

Recommended fix Moderate confidence

HPE iMC PLAT 7.2 E0403P07 or later patch, or upgrade to iMC PLAT 7.3 or newer major version

  1. Identify current HPE iMC PLAT version via the administration console or system information
  2. Contact HPE support or access the HPE security bulletin for CVE-2017-5791 to obtain the specific patch
  3. Apply the recommended patch (typically a later E0403Pxx version) to the iMC PLAT 7.2 deployment
  4. Verify the patch was applied successfully by checking the version information
  5. Test that authentication is properly enforced for all URIs that should require authentication
Caveat Review HPE release notes for any compatibility or configuration changes in the patch version

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

Fix this in Intelligent Management Center Plat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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