Webex TeamsApplication · Cisco
CVE-2020-3535
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 · uneditedA vulnerability in the loading mechanism of specific DLLs in the Cisco Webex Teams client for Windows could allow an authenticated, local attacker to load a malicious library. To exploit this vulnerability, the attacker needs valid credentials on the Windows system. The vulnerability is due to incorrect handling of directory paths at run time. An attacker could exploit this vulnerability by placing a malicious DLL file in a specific location on the targeted system. This file will execute when the vulnerable application launches. A successful exploit could allow the attacker to execute arbitrary code on the targeted system with the privileges of another user’s account.
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 confidenceDLL hijacking vulnerability in Cisco Webex Teams client for Windows where an authenticated local attacker can place a malicious DLL in a specific directory that the application loads from at runtime, allowing arbitrary code execution with the privileges of the user who launches Webex.
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
>= 3.0.13464.0, <= 3.0.16040.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Cisco Webex Teams is installedCheck for Cisco Webex Teams installation on Windows by looking in Program Files or Program Files (x86) for a Webex Teams folder, or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Webex TeamsAffected if The application is installed on the system
-
Determine installed Webex Teams versionRight-click the Webex Teams executable (typically at C:\Program Files\Webex\Webex Teams\WebexTeams.exe) and select Properties, then view the Details tab to find the Product VersionAffected if The version falls within the range 3.0.13464.0 through 3.0.16040.0 inclusive
-
Identify the DLL loading directoryExamine the Webex Teams installation directory (commonly C:\Program Files\Webex\Webex Teams\) for any unexpected or suspicious DLL files that were not part of a legitimate installationAffected if Unknown or untrusted DLL files are present in the application directory that could be loaded at runtime
-
Compare version against affected rangeIf a version was obtained from step 2, verify whether it is greater than or equal to 3.0.13464.0 AND less than or equal to 3.0.16040.0Affected if The installed version is within the affected range, meaning the DLL hijacking vulnerability is present
A user is affected if Cisco Webex Teams is installed with a version between 3.0.13464.0 and 3.0.16040.0 and untrusted DLL files could be placed in the application's directory for hijacking.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Cisco's patch for this vulnerability when available; until then, restrict local user permissions and monitor for suspicious DLL files in Webex installation directories.
Fix this in Webex Teams
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3535 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-3535 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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