dbcve.org
Hosted Collaboration Mediation FulfillmentApplication · Cisco

CVE-2016-6371

HIGH · 7.5 CVSS v3.0 Published 2016-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Directory traversal vulnerability in the web interface in Cisco Hosted Collaboration Mediation Fulfillment (HCM-F) 10.6(3) and earlier allows remote attackers to write to arbitrary files via a crafted URL, aka Bug ID CSCuz64717.

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

Directory traversal vulnerability in the Cisco HCM-F web interface allows remote unauthenticated attackers to write to arbitrary files on the server by using path traversal sequences (../) in crafted URLs. This can enable remote code execution or complete system compromise.

MitigationApply the Cisco patch/upgrade to a fixed version (10.6(4) or later) per vendor advisories. As interim mitigation, deploy WAF rules to block directory traversal patterns in HTTP requests.

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
Hosted Collaboration Mediation FulfillmentApplication
Affected:= 10.6\(1\)_base= 10.6\(2\)_base= 10.6\(3\)_base

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
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 installed Cisco HCM-F version
    Access the Cisco HCM-F administrative interface or use the system CLI/management console to retrieve the current software version. This is typically found in 'show version' output or within the web UI's system information page.
    Affected if The installed version equals 10.6(1)_base, 10.6(2)_base, or 10.6(3)_base exactly as listed in the affected versions.
  2. Confirm the HCM-F web interface is enabled and exposed
    Verify whether the Cisco HCM-F web interface (HTTP/HTTPS) is accessible from network locations. Check the web server configuration or listener status.
    Affected if The web interface is running and reachable on any network interface, as this is the attack vector.
  3. Review web access logs for directory traversal patterns
    Examine HTTP access logs for the HCM-F web server, looking for URL patterns containing '../' or path traversal sequences. Search for requests attempting to access files outside the web root.
    Affected if Any logs show unauthenticated HTTP requests with '../' sequences targeting the web interface.
  4. Check for unauthorized files written to the system
    Inspect the file system for unexpected or newly created files in web-accessible directories or system directories that were not deployed as part of normal HCM-F operation.
    Affected if Unexpected files exist that correlate with the timing of the vulnerability disclosure or show contents consistent with remote code execution.
  5. Verify no unauthorized user accounts or configurations exist
    Review user accounts, authentication configurations, and any modified system scripts or cron jobs that may indicate post-exploitation activity.
    Affected if New administrative accounts, modified scripts, or suspicious scheduled tasks are present.

You are affected if the installed Cisco HCM-F version is exactly 10.6(1)_base, 10.6(2)_base, or 10.6(3)_base AND the web interface is exposed, or if logs/files show evidence of directory traversal exploitation.

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

Apply the Cisco patch/upgrade to a fixed version (10.6(4) or later) per vendor advisories. As interim mitigation, deploy WAF rules to block directory traversal patterns in HTTP requests.

Fix this in Hosted Collaboration Mediation Fulfillment Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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