dbcve.org
FinesseApplication · Cisco

CVE-2016-1373

HIGH · 8.6 CVSS v3.0 Published 2016-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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
The gadgets-integration API in Cisco Finesse 8.5(1) through 8.5(5), 8.6(1), 9.0(1), 9.0(2), 9.1(1), 9.1(1)SU1, 9.1(1)SU1.1, 9.1(1)ES1 through 9.1(1)ES5, 10.0(1), 10.0(1)SU1, 10.0(1)SU1.1, 10.5(1), 10.5(1)ES1 through 10.5(1)ES4, 10.5(1)SU1, 10.5(1)SU1.1, 10.5(1)SU1.7, 10.6(1), 10.6(1)SU1, 10.6(1)SU2, and 11.0(1) allows remote attackers to conduct server-side request forgery (SSRF) attacks via a crafted request, aka Bug ID CSCuw86623.

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 vulnerability exists in the gadgets-integration API of Cisco Finesse, a contact center collaboration platform. Remote attackers can conduct Server-Side Request Forgery (SSRF) attacks by sending crafted requests to the API, potentially allowing them to make the server initiate requests to internal or external resources.

MitigationApply the relevant Cisco security patch for this vulnerability (refer to CSCuw86623). If immediate patching is not feasible, implement network segmentation and restrict outbound access from the Finesse server to limit SSRF impact.

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
FinesseApplication
Affected:= 8.5\(1\)_base= 8.5\(2\)_base= 8.5\(3\)_base= 8.5\(4\)_base= 8.5\(5\)_base= 8.6\(1\)_base= 9.0\(1\)_base= 9.0\(2\)_base= 9.1\(1\)_base= 9.1\(1\)_es1= 9.1\(1\)_es2= 9.1\(1\)_es3

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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. Confirm Cisco Finesse is installed
    Check for Cisco Finesse installation by looking for the Finesse web application directory or checking running services on the server. Common paths include /opt/finesse or check for finesse-related processes.
    Affected if Cisco Finesse is not present on the system, the system is not affected by this vulnerability.
  2. Identify installed Finesse version
    Access the Finesse administration console or check the version file. The version can typically be found in the Finesse desktop URL or by accessing the /finesse/api/systemInfo endpoint if the service is running.
    Affected if The installed version matches one of the affected versions: 8.5(1), 8.5(2), 8.5(3), 8.5(4), 8.5(5), 8.6(1), 9.0(1), 9.0(2), 9.1(1), 9.1(1)_es1, 9.1(1)_es2, or 9.1(1)_es3.
  3. Verify gadgets-integration API is accessible
    Check if the /gadgets/ API endpoint is exposed by attempting to access the Finesse server on common ports (typically 443 or 8443) and reviewing the URL structure for gadget-related endpoints.
    Affected if The gadgets-integration API endpoint is reachable from a network where an attacker could send crafted requests.
  4. Review API exposure and network access
    Examine firewall rules, reverse proxy configurations, and access control lists to determine if the Finesse gadgets-integration API is exposed to untrusted networks or the internet.
    Affected if The API is accessible from untrusted networks, increasing the likelihood of successful SSRF exploitation.

The environment is affected if Cisco Finesse is installed and the version matches any of the listed affected versions (8.5 through 9.1(1)_es3) with the gadgets-integration API 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.

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

Apply the relevant Cisco security patch for this vulnerability (refer to CSCuw86623). If immediate patching is not feasible, implement network segmentation and restrict outbound access from the Finesse server to limit SSRF impact.

Fix this in Finesse Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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