dbcve.org
Intelligent Management Center Wireless Services Manager SoftwareApplication · Hp

CVE-2018-7104

CRITICAL · 9.8 CVSS v3.0 Published 2018-09-27
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 Services Manager Software earlier than version IMC WSM 7.3 E0506P02.

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 Wireless Services Manager allows unauthenticated attackers to execute arbitrary code on affected systems via network exploit. The vulnerability exists in versions prior to IMC WSM 7.3 E0506P02, likely due to inadequate input validation or authentication controls in the WSM component.

MitigationUpgrade HPE iMC Wireless Services Manager to version IMC WSM 7.3 E0506P02 or later. 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
Intelligent Management Center Wireless Services Manager SoftwareApplication
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 installation
    Check if HPE Intelligent Management Center is installed on the system. Look for the installation directory (typically under C:\Program Files\HPE\iMC or similar locations) or check Windows Programs and Features for HPE iMC entries.
    Affected if HPE Intelligent Management Center software is found on the system
  2. Determine iMC WSM version
    Locate the Wireless Services Manager component within the iMC installation. Check version information in the WSM module's about or version file, or access the iMC web interface and navigate to the WSM component to view its version number.
    Affected if The WSM component version is 7.3 or lower (including all versions below 7.3)
  3. Confirm WSM component is active
    Verify that the Wireless Services Manager module is enabled and accessible. This can be done by checking if the WSM service is running, or by attempting to access the WSM web interface at the typical iMC management URL.
    Affected if The WSM component is installed and actively running
  4. Check for network exposure
    Determine if the iMC management interfaces (port 8080 or 8443 typically) are exposed to untrusted networks. Review firewall rules and network configurations to assess external accessibility.
    Affected if The iMC management interface is reachable from untrusted networks (optional context for exploitation)

A system is affected if HPE Intelligent Management Center with Wireless Services Manager version 7.3 or lower is installed and the WSM component is active.

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 Wireless Services Manager to version IMC WSM 7.3 E0506P02 or later. 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

IMC WSM 7.3 E0506P02 or later

  1. Navigate to the HPE support website (support.hpe.com) and search for HPE Intelligent Management Center (iMC)
  2. Locate the Wireless Services Manager (WSM) component downloads
  3. Download IMC WSM version 7.3 E0506P02 or later
  4. Review the HPE release notes and installation guide for prerequisites
  5. Ensure backup of current configuration data
  6. Stop the iMC services before upgrading
  7. Install the updated IMC WSM 7.3 E0506P02 software
  8. Restart iMC services after successful installation
Caveat Review HPE compatibility matrices for dependencies with other IMC components before upgrading

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

Fix this in Intelligent Management Center Wireless Services Manager Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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