dbcve.org
JabberApplication · Cisco

CVE-2017-12358

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 authenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based management interface. 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 malicious 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: CSCvf79080, CSCvf79088.

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

Cross-site scripting (XSS) vulnerability in Cisco Jabber's web-based management interface. An authenticated attacker can inject malicious script through insufficiently validated user input, which executes when users access the affected interface, allowing arbitrary JavaScript execution in the browser context.

MitigationApply Cisco security updates for Cisco Jabber addressing CSCvf79080 and CSCvf79088. Until patches are applied, disable or restrict access to the web-based management interface and train users to avoid clicking untrusted links.

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= 11.9\(0\)

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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. Confirm Cisco Jabber installation
    Check for Cisco Jabber installation by looking in standard program directories (Windows: C:\Program Files\Cisco Systems\Cisco Jabber or C:\Program Files (x86)\Cisco Systems\Cisco Jabber), or search for 'Jabber' in Add/Remove Programs. On Linux, check /opt/cisco/jabber or using package manager commands like dpkg -l | grep -i jabber or rpm -qa | grep -i jabber.
    Affected if Cisco Jabber software is found installed on the system
  2. Determine installed Cisco Jabber version
    Open Cisco Jabber and navigate to Help > About, or check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Install\InstallDir for the path, then check the version.xml or version.txt in the installation directory. On Linux, run: /opt/cisco/jabber/jabber --version
    Affected if The installed version matches any version of Cisco Jabber (the advisory indicates all versions are affected)
  3. Verify web-based management interface is enabled
    Access the web-based management interface by opening a browser and navigating to https://localhost:443 or the configured management port (default 443). Check Cisco Jabber configuration files (jabber-config.xml or config.xml in the installation directory) for webAdminEnabled or similar settings. On Windows, also check registry: HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Cisco Jabber\AdminEnabled
    Affected if The web-based management interface is enabled and accessible (this is the attack vector for the XSS vulnerability)
  4. Confirm network accessibility of management interface
    If the web interface is locally enabled, verify if it is bound to external interfaces by checking the configuration for listenAddress or adminInterface settings. Test by attempting to access the interface from another host: https://<jabber-server-ip>:443/admin
    Affected if The web-based management interface is accessible over the network (increases exposure to remote attackers)

A user is affected if Cisco Jabber is installed and its web-based management interface is enabled and accessible, regardless of version since all versions are listed as affected.

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 Cisco security updates for Cisco Jabber addressing CSCvf79080 and CSCvf79088. Until patches are applied, disable or restrict access to the web-based management interface and train users to avoid clicking untrusted links.

Fix this in Jabber Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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