dbcve.org
JabberApplication · Cisco

CVE-2018-0199

MEDIUM · 6.1 CVSS v3.0 Published 2018-02-22
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 Cisco Jabber Client Framework (JCF) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of an affected device. The vulnerability is due to improper neutralization of script in attributes in a web page. An attacker could exploit this vulnerability by executing arbitrary JavaScript in the Jabber client of the recipient. An exploit could allow the attacker to perform remote code execution. Cisco Bug IDs: CSCve53989.

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

This is a cross-site scripting (XSS) vulnerability in Cisco Jabber Client Framework caused by improper neutralization of script in attributes. An unauthenticated remote attacker can inject malicious JavaScript that executes within a user's Jabber client, potentially achieving remote code execution.

MitigationApply the vendor patch from Cisco (CSCve53989) when available. Until then, restrict Jabber communications to trusted sources and monitor for unusual client behavior.

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

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. Verify Cisco Jabber is installed
    Check for Cisco Jabber installation: On Windows, look in Program Files for 'Cisco Systems' folder containing 'Cisco Jabber'; On Mac, check /Applications for 'Cisco Jabber.app'
    Affected if Cisco Jabber is present on the system
  2. Identify installed Cisco Jabber version
    Open Cisco Jabber, go to Help > About Cisco Jabber, or right-click the Jabber icon and select 'About'. Alternatively, check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Cisco Jabber} for DisplayVersion, or on Mac check the app bundle info.plist for CFBundleShortVersionString
    Affected if The version displayed is 11.9 or 11.9(0) or falls within an unpatched version range
  3. Confirm Jabber client is configured and active
    Check if Jabber has been configured with an account by examining %APPDATA%\Cisco\Unified Communications\Jabber\CSF\Config (Windows) or ~/Library/Application Support/Cisco/Jabber/CSF/Config (Mac) for configuration XML files
    Affected if Jabber is configured and the client has been used to connect to a server, enabling the vulnerable Client Framework component
  4. Inspect for indicators of XSS exploitation
    Review Jabber client logs at %APPDATA%\Cisco\Unified Communications\Jabber\CSF\Logs (Windows) or ~/Library/Logs/Cisco/Jabber/CSF/ (Mac) for unusual script tags, unexpected JavaScript references, or malformed message content in XML logs
    Affected if Log entries show injected script content or unexpected attribute values in message handling

A user is affected if Cisco Jabber version 11.9 or 11.9(0) is installed and the client has been configured or used, as the XSS vulnerability in the Client Framework can be triggered through message processing.

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 from Cisco (CSCve53989) when available. Until then, restrict Jabber communications to trusted sources and monitor for unusual client behavior.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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