dbcve.org
FinesseApplication · Cisco

CVE-2018-0398

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Multiple vulnerabilities in the web-based management interface of Cisco Finesse could allow an unauthenticated, remote attacker to conduct a server-side request forgery (SSRF) attack. Cisco Bug IDs: CSCvg71018.

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

Multiple SSRF vulnerabilities in Cisco Finesse's web-based management interface allow unauthenticated remote attackers to make the server perform arbitrary requests on their behalf by manipulating input parameters, potentially enabling internal network reconnaissance or access to internal services.

MitigationApply the vendor patch when available; until then, restrict access to the Finesse management interface to trusted networks only using network segmentation and firewall rules, and monitor for suspicious outbound requests from the Finesse server.

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:= 11.5\(1\)

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. Confirm Cisco Finesse is installed
    Look for the Finesse application on the system, typically installed on a server (often VMware virtual appliance or as part of Cisco Unified Communications Manager). Check for the Finesse web service listening on common ports like 443 or 8080.
    Affected if Cisco Finesse software is running on the system
  2. Identify the installed version
    Access the Finesse web interface and navigate to the About page, typically at https://<finesse-server>/finesse/about, or check the version via the Finesse administration console. The version is displayed as 11.5(1) or similar.
    Affected if The version shown is exactly 11.5(1)
  3. Verify the management interface is accessible
    Attempt to access the Finesse web-based management interface via HTTP/HTTPS. The vulnerability exists in the management interface endpoints. Check if the /finesse or /ccp (Cisco Configuration Professional) management paths respond.
    Affected if The management interface is reachable over the network
  4. Assess network exposure
    Determine if the Finesse management interface is exposed to untrusted networks by reviewing firewall rules, ACLs, and network segmentation. Check if the management ports are accessible from outside the trusted network segment.
    Affected if The management interface is accessible from untrusted networks or the internet
  5. Review outbound traffic logs
    Examine server logs and network logs for suspicious outbound requests originating from the Finesse server to internal resources, external IPs, or unusual endpoints that were not initiated by legitimate administrators.
    Affected if Unexpected outbound HTTP/HTTPS requests are observed from the Finesse server

You are affected if Cisco Finesse version 11.5(1) is installed and its web-based management interface is accessible over the network, allowing unauthenticated attackers to manipulate input parameters to make the server perform arbitrary requests.

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 vendor patch when available; until then, restrict access to the Finesse management interface to trusted networks only using network segmentation and firewall rules, and monitor for suspicious outbound requests from the Finesse server.

Fix this in Finesse Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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