dbcve.org
JabberApplication · Cisco

CVE-2017-12356

MEDIUM · 6.1 CVSS v3.0 Published 2017-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 vulnerability in the web-based management interface of Cisco Jabber for Windows, Mac, Android, and iOS could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based information. Cisco Bug IDs: CSCvf50378, CSCvg56018.

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

This is a reflected Cross-Site Scripting (XSS) vulnerability in the web-based management interface of Cisco Jabber across Windows, Mac, Android, and iOS platforms. The vulnerability stems from insufficient validation of user-supplied input, allowing an unauthenticated remote attacker to inject malicious scripts via a crafted link. Successful exploitation enables arbitrary script execution in the context of the interface or access to sensitive browser-based information.

MitigationApply the vendor-provided security update from Cisco to address the input validation flaw in the web-based management interface. Users should avoid clicking untrusted links until the patch is deployed.

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
JabberApplication
Affected:all versions= 10.5\(2\)= 11.9\(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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Cisco Jabber installations
    Search all systems for Cisco Jabber client installations. On Windows, check Program Files/Cisco Systems/Cisco Jabber or use: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Jabber*'}. On Mac, check /Applications for Cisco Jabber.app.
    Affected if Cisco Jabber software is found on any system in the environment
  2. Determine installed version
    Locate the version information. On Windows, right-click the Jabber executable, select Properties, then Details. Or run: (Get-Item 'C:\Program Files\Cisco Systems\Cisco Jabber\Cisco Jabber.exe').VersionInfo. On Mac, right-click Cisco Jabber.app, Get Info, or run: defaults read /Applications/Cisco\ Jabber.app/Contents/Info CFBundleVersion.
    Affected if The installed version matches or falls within affected ranges including 10.5(2) and 11.9(1)
  3. Verify web management interface status
    Check if the embedded HTTP server is enabled. On Windows, examine the Jabber configuration file (typically in %APPDATA%\Cisco\Unified Communications\Jabber\CSF\Config or %PROGRAMDATA%\Cisco\Unified Communications\Jabber\CSF\Config) for HTTPEnable or similar settings.
    Affected if The web-based management interface is enabled and accessible
  4. Assess network exposure
    Determine if the management interface port (default 8080 or 443) is accessible from outside the local machine or untrusted networks. Use netstat -an | findstr :8080 or check firewall rules.
    Affected if The interface is reachable from untrusted network segments or the internet

You are affected if Cisco Jabber is installed with an affected version (including 10.5(2) and 11.9(1)) AND the web-based management interface is enabled and accessible, allowing an attacker to deliver a crafted link.

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-provided security update from Cisco to address the input validation flaw in the web-based management interface. Users should avoid clicking untrusted links until the patch is deployed.

Fix this in Jabber Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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