dbcve.org
Webex TeamsApplication · Cisco

CVE-2024-20396

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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 protocol handlers of Cisco Webex App could allow an unauthenticated, remote attacker to gain access to sensitive information. This vulnerability exists because the affected application does not safely handle file protocol handlers. An attacker could exploit this vulnerability by persuading a user to follow a link that is designed to cause the application to send requests. If the attacker can observe transmitted traffic in a privileged network position, a successful exploit could allow the attacker to capture sensitive information, including credential information, from the requests.

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

A protocol handler vulnerability in Cisco Webex App allows an unauthenticated remote attacker to capture sensitive information. The app does not safely handle file protocol handlers, and attackers exploit this by tricking users into following malicious links that cause the application to send requests. If an attacker occupies a privileged network position, they can intercept these requests and harvest credential information.

MitigationApply the vendor patch when available; until then, enforce network segmentation to prevent privileged network position attacks and educate users about not 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
Webex TeamsApplication
Affected:= 3.0.13464.0= 3.0.13538.0= 3.0.13588.0= 3.0.14154.0= 3.0.14234.0= 3.0.14375.0= 3.0.14741.0= 3.0.14866.0= 3.0.15015.0= 3.0.15036.0= 3.0.15092.0= 3.0.15131.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Cisco Webex Teams version
    On Windows, open Programs and Features or check Add/Remove Programs to find the version. On macOS, right-click the Webex Teams app in Applications and select Get Info to view the version.
    Affected if The installed version matches any of these exact versions: 3.0.13464.0, 3.0.13538.0, 3.0.13588.0, 3.0.14154.0, 3.0.14234.0, 3.0.14375.0, 3.0.14741.0, 3.0.14866.0, 3.0.15015.0, 3.0.15036.0, 3.0.15092.0, or 3.0.15131.0
  2. Confirm protocol handler registration
    On Windows, check registry key HKEY_CLASSES_ROOT\webex or similar webex:// protocol entries. On macOS, check ~/Library/Application Support/Webex/ or the app bundle for handler configurations.
    Affected if The webex:// protocol handler is registered and the application processes links without additional safety prompts
  3. Verify user awareness of link clicking
    Review user training records or conduct a brief survey to determine if users understand risks of clicking untrusted webex:// links from external sources.
    Affected if Users may unknowingly click malicious links that trigger automatic request sending by the application
  4. Assess network position risk
    Determine if untrusted or potentially compromised devices can occupy a network position between users and authentication endpoints (for example, through ARP spoofing, rogue access points, or man-in-the-middle proxies).
    Affected if An attacker with privileged network position could intercept requests containing credential information sent by the application

You are affected if Cisco Webex Teams is installed at any of the twelve specific versions listed AND the webex:// protocol handler is active, allowing an attacker who tricks a user into clicking a malicious link to intercept sensitive requests if they occupy a privileged network position.

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 when available; until then, enforce network segmentation to prevent privileged network position attacks and educate users about not clicking untrusted links.

Fix this in Webex Teams 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-2024-20396 — 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-2024-20396 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