dbcve.org
JabberApplication · Cisco

CVE-2020-3537

MEDIUM · 5.7 CVSS v3.1 Published 2020-09-04
Fix available
A fix is available. Upgrade to 12.1.3 / 12.5.2 or later.
See remediation →
61/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 Cisco Jabber for Windows software could allow an authenticated, remote attacker to gain access to sensitive information. The vulnerability is due to improper validation of message contents. An attacker could exploit this vulnerability by sending specially crafted messages that contain Universal Naming Convention (UNC) links to a targeted user and convincing the user to follow the provided link. A successful exploit could allow the attacker to cause the application to access a remote system, possibly allowing the attacker to gain access to sensitive information that the attacker could use in additional attacks.

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

Cisco Jabber for Windows improperly validates message contents, specifically Universal Naming Convention (UNC) links. When a user follows a crafted UNC link sent via messaging, the application accesses a remote system, potentially exposing sensitive information to the attacker.

MitigationApply the vendor-provided patch when available. In the interim, users should be trained to not follow untrusted UNC links received via Jabber messages.

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:>= 12.1, < 12.1.3>= 12.5, < 12.5.2>= 12.6, < 12.6.3>= 12.7, < 12.7.2>= 12.8, < 12.8.3>= 12.9, < 12.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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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 if Cisco Jabber for Windows is installed
    Open PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*', 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object { $_.DisplayName -like '*Cisco Jabber*' } | Select-Object DisplayName, DisplayVersion
    Affected if No Cisco Jabber for Windows entry is found in the installed programs registry
  2. Determine the installed version of Cisco Jabber
    Locate the Jabber executable (typically at C:\Program Files\Cisco Systems\Cisco Jabber\Jabber.exe) or C:\Program Files (x86)\Cisco Systems\Cisco Jabber\Jabber.exe, right-click the file, select Properties, and check the Details tab for the Product Version
    Affected if The version displayed does not match any of the fixed versions (12.1.3, 12.5.2, 12.6.3, 12.7.2, 12.8.3, 12.9.1 or higher)
  3. Compare your version against the affected ranges
    If the version is 12.1.x, it is affected unless it is 12.1.3 or higher. For 12.5.x, affected unless 12.5.2 or higher. For 12.6.x, affected unless 12.6.3 or higher. For 12.7.x, affected unless 12.7.2 or higher. For 12.8.x, affected unless 12.8.3 or higher. For 12.9.x, affected unless 12.9.1 or higher
    Affected if The installed version falls within any of these ranges: 12.1 to 12.1.2, 12.5 to 12.5.1, 12.6 to 12.6.2, 12.7 to 12.7.1, 12.8 to 12.8.2, or 12.9.0

You are affected if Cisco Jabber for Windows is installed and its version number is within any of the vulnerable version ranges listed above.

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
Upgrade available Upgrade to 12.1.3 / 12.5.2 / 12.6.3 or later
Fixed in 12.1.312.5.212.6.3
Interim mitigation

Apply the vendor-provided patch when available. In the interim, users should be trained to not follow untrusted UNC links received via Jabber messages.

Fix this in Jabber Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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