It InstallerApplication · Zoom

CVE-2020-11443

HIGH · 8.1 CVSS v3.1 Published 2020-05-04
Fix available
A fix is available. Upgrade to 4.6.10 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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
The Zoom IT installer for Windows (ZoomInstallerFull.msi) prior to version 4.6.10 deletes files located in %APPDATA%\Zoom before installing an updated version of the client. Standard users are able to write to this directory, and can write links to other directories on the machine. As the installer runs with SYSTEM privileges and follows these links, a user can cause the installer to delete files that otherwise cannot be deleted by the user.

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

The Zoom IT installer for Windows (ZoomInstallerFull.msi) prior to version 4.6.10 deletes files in %APPDATA%\Zoom before installing an update. Standard users can write to this directory and create symbolic links to other locations. Since the installer runs with SYSTEM privileges and follows these symlinks, an unprivileged user can cause the installer to delete files in protected directories they normally cannot access, enabling local privilege escalation.

MitigationUpdate to Zoom version 4.6.10 or later. Ensure IT-managed deployments use the patched installer to prevent local privilege escalation via symlink attacks.

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
It InstallerApplication
Affected:< 4.6.10

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Locate the Zoom IT installer file
    Search for ZoomInstallerFull.msi on your system, typically found in IT deployment shares, software distribution folders, or download directories. Right-click the file, select Properties, and check the Details tab for the version information.
    Affected if The installer version shown is less than 4.6.10 (for example, 4.6.9 or earlier)
  2. Check if Zoom has been installed or updated via the IT installer
    Open File Explorer and navigate to %APPDATA%\Zoom. Verify this directory exists, which indicates the Zoom client has been installed or updated.
    Affected if The %APPDATA%\Zoom directory exists and the installer used was version prior to 4.6.10
  3. Verify directory permissions on the Zoom appdata folder
    Right-click the %APPDATA%\Zoom folder, select Properties, then Security tab. Check if standard (non-admin) users have Write or Modify permissions to this directory.
    Affected if Standard users have Write or Modify permissions to %APPDATA%\Zoom and the vulnerable installer was used
  4. Identify the installed Zoom client version from the installer log
    Check Windows Installer logs in %TEMP% or %APPDATA%\Zoom\logs for installation records that show which installer version was used for the last update.
    Affected if Log files show the installer version was less than 4.6.10

Your environment is affected if the Zoom IT installer (ZoomInstallerFull.msi) version used to deploy or update Zoom is below 4.6.10 and standard users can write to the %APPDATA%\Zoom directory.

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 4.6.10 or later
Fixed in 4.6.10
Interim mitigation

Update to Zoom version 4.6.10 or later. Ensure IT-managed deployments use the patched installer to prevent local privilege escalation via symlink attacks.

Fix this in It Installer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-11443 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