dbcve.org
Imc Wireless Service ManagerApplication · Hp

CVE-2017-8990

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-06
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 was identified in HPE Intelligent Management Center (iMC) Wireless Service Manager (WSM) Software earlier than version WSM 7.3 (E0506). This issue was resolved in HPE IMC Wireless Services Manager Software IMC WSM 7.3 E0506P01 or subsequent version.

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 exists in HPE Intelligent Management Center Wireless Service Manager (WSM) Software versions earlier than 7.3 (E0506). The vulnerability allows attackers to execute arbitrary code remotely on affected systems, likely through the WSM component's network-facing interface.

MitigationUpgrade HPE IMC WSM to version 7.3 E0506P01 or subsequent version. If immediate patching is not possible, restrict network access to the iMC management interfaces and implement additional monitoring for suspicious activity.

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
Imc Wireless Service ManagerApplication
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. Identify HPE IMC WSM installation
    Locate the HPE Intelligent Management Center installation directory and check for the Wireless Service Manager (WSM) component. Common paths include the HPE iMC installation folder. Use system inventory tools or check Add/Remove Programs on Windows for 'HPE Intelligent Management Center' or 'HPE IMC WSM'.
    Affected if HPE IMC WSM is installed and the version is earlier than 7.3 or equals exactly 7.3
  2. Confirm installed WSM version
    Access the HPE IMC web interface or check the WSM component version through the IMC platform's version information page. Typically found under 'System' > 'System Information' or similar in the management console. Alternatively, check version files in the WSM installation directory if accessible.
    Affected if The displayed version is < 7.3 or = 7.3 (any 7.3.x release)
  3. Verify WSM component is enabled
    Log into the HPE IMC administration console and navigate to the Wireless Service Manager module. Check if the WSM service is deployed and running within the IMC platform. This is typically found under 'Services' or 'Component Management' in the IMC interface.
    Affected if WSM component is deployed and running on the IMC platform
  4. Assess network exposure of IMC management interfaces
    Review firewall rules, network configurations, and access control lists to determine if the HPE IMC web management interface (typically ports 8080, 8443, or similar) is accessible from untrusted networks or the internet. Use network scanning tools to identify exposed IMC ports.
    Affected if The IMC management interface with WSM is accessible from untrusted networks or directly from the internet

A system is affected if HPE IMC WSM version 7.3 or any version earlier than 7.3 is installed, the WSM component is enabled, and the management interface is network-accessible to potential attackers.

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 WSM to version 7.3 E0506P01 or subsequent version. If immediate patching is not possible, restrict network access to the iMC management interfaces and implement additional monitoring for suspicious activity.

Recommended fix High confidence

WSM 7.3 E0506P01 or subsequent version

  1. Back up the current HPE iMC configuration and database before upgrading
  2. Download HPE IMC Wireless Services Manager Software version WSM 7.3 E0506P01 or subsequent from HPE Support (support.hpe.com)
  3. Stop all HPE iMC services on the affected server
  4. Install the WSM 7.3 E0506P01 version following HPE's standard upgrade documentation
  5. Restart HPE iMC services and verify the Wireless Service Manager component is operational
  6. Confirm the version by checking the WSM component version in the IMC platform

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

Fix this in Imc Wireless Service Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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