dbcve.org
HealthcenterApplication · Healthcenter Project

CVE-2016-10684

HIGH · 8.1 CVSS v3.0 Published 2018-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
healthcenter - IBM Monitoring and Diagnostic Tools health Center agent healthcenter downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested resources with an attacker controlled copy if the attacker is on the network or positioned in between the user and the remote server.

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 · high confidence

The IBM Monitoring and Diagnostic Tools healthcenter agent downloads binary resources over unencrypted HTTP, allowing network attackers to intercept and replace these binaries with malicious versions via Man-In-The-Middle attacks, potentially achieving remote code execution.

MitigationMigrate all binary resource downloads from HTTP to HTTPS with proper SSL/TLS certificate validation to ensure integrity and prevent tampering. Verify that downloaded binaries are from legitimate sources before execution.

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
HealthcenterApplication
Affected:= 3.0.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/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 if IBM Healthcenter is installed
    Check for IBM Monitoring and Diagnostic Tools or Healthcenter agent installations on the system. Look for directories or services named 'healthcenter' or 'IBM\IMShared\tools' in Program Files.
    Affected if The product is present on the system
  2. Determine the installed Healthcenter version
    Use the system package manager, or check the product's 'about' information, manifest, or version file. Common locations include installation directories with a 'version' or '.version' file, or use the product's CLI if available (e.g., 'healthcenter version' command).
    Affected if The installed version is 3.0.3 exactly, or falls within the affected version range containing 3.0.3
  3. Inspect download source configuration
    Examine configuration files in the Healthcenter installation directory for URLs that specify HTTP (not HTTPS) endpoints. Look for files like 'download.config', 'repository.xml', 'site.xml', or similar that define where binaries are fetched from.
    Affected if Download URLs use 'http://' instead of 'https://'
  4. Check agent or tool network settings
    Review Healthcenter agent configuration files for any settings controlling update, plugin, or binary download behavior. Look for properties related to 'updateUrl', 'downloadUrl', 'repository', or 'pluginServer'.
    Affected if The configuration specifies non-SSL/HTTP-based download locations
  5. Review proxy or network traffic settings
    If Healthcenter uses a proxy or has network configuration, check whether it enforces SSL/TLS or allows plain HTTP connections for fetching resources.
    Affected if HTTP is permitted for remote resource downloads without TLS/SSL enforcement

A defender is affected if IBM Healthcenter version 3.0.3 (or an affected version including 3.0.3) is installed AND the product is configured to download binaries over unencrypted HTTP URLs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Migrate all binary resource downloads from HTTP to HTTPS with proper SSL/TLS certificate validation to ensure integrity and prevent tampering. Verify that downloaded binaries are from legitimate sources before execution.

Fix this in Healthcenter Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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