dbcve.org
JabberApplication · Cisco

CVE-2020-3430

HIGH · 8.8 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 →
95/100
Remediation priority · Urgent
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 application protocol handling features of Cisco Jabber for Windows could allow an unauthenticated, remote attacker to execute arbitrary commands. The vulnerability is due to improper handling of input to the application protocol handlers. An attacker could exploit this vulnerability by convincing a user to click a link within a message sent by email or other messaging platform. A successful exploit could allow the attacker to execute arbitrary commands on a targeted system with the privileges of the user account that is running the Cisco Jabber client software.

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 contains a vulnerability in its application protocol handler that allows unauthenticated remote attackers to execute arbitrary commands by tricking users into clicking malicious links sent via email or messaging platforms. The attacker does not need authentication and can execute commands with the same privileges as the logged-on user running the Jabber client.

MitigationApply the vendor patch from Cisco for Cisco Jabber for Windows. Until patched, users should be trained to avoid clicking untrusted links, and organizations may consider network-level controls to block known malicious patterns.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Cisco Jabber for Windows is installed
    Open Control Panel > Programs and Features, or run 'wmic product get name,version' to list installed software, and look for 'Cisco Jabber' in the list
    Affected if Cisco Jabber for Windows appears in the installed programs list
  2. Determine the installed version of Cisco Jabber
    In Programs and Features, click on Cisco Jabber and view the Version column, or right-click the executable (typically in C:\Program Files\Cisco Systems\Cisco Jabber\) and select Properties > Details to see the File Version
    Affected if The version shown is one of the affected versions: 12.1 through 12.1.2, 12.5.0 through 12.5.1, 12.6.0 through 12.6.2, 12.7.0 through 12.7.1, 12.8.0 through 12.8.2, or 12.9.0
  3. Compare your version against the affected ranges
    If the version starts with 12.1, 12.5, 12.6, 12.7, 12.8, or 12.9, check if it is lower than the fixed versions: 12.1.3, 12.5.2, 12.6.3, 12.7.2, 12.8.3, or 12.9.1 respectively
    Affected if Your installed version falls within any of these ranges and is therefore vulnerable

If Cisco Jabber for Windows is installed and its version is 12.1.x before 12.1.3, 12.5.x before 12.5.2, 12.6.x before 12.6.3, 12.7.x before 12.7.2, 12.8.x before 12.8.3, or 12.9.x before 12.9.1, your environment is affected by this vulnerability.

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 patch from Cisco for Cisco Jabber for Windows. Until patched, users should be trained to avoid clicking untrusted links, and organizations may consider network-level controls to block known malicious patterns.

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 the upgrade done

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-2020-3430 — 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-3430 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