dbcve.org
ZoomApplication

CVE-2024-27242

MEDIUM · 6.8 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 5.7.10 or later.
See remediation →
72/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
Cross site scripting in Zoom Desktop Client for Linux before version 5.17.10 may allow an authenticated user to conduct a denial of service via network access.

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

Cross-site scripting (XSS) vulnerability in Zoom Desktop Client for Linux versions prior to 5.17.10 allows an authenticated user to inject malicious scripts that may result in denial of service via network access. The vulnerability requires user authentication to exploit.

MitigationUpgrade Zoom Desktop Client for Linux to version 5.17.10 or later. Organizations should deploy the updated client version through their patch management systems and verify successful remediation.

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
ZoomApplication
Affected:< 5.7.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
Required
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:N/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. Confirm Zoom Desktop Client for Linux is installed
    Check for Zoom installation by looking for the zoom package or executable. On Linux, you can run 'dpkg -l | grep zoom' for Debian-based systems or 'rpm -qa | grep zoom' for RHEL-based systems. Alternatively, check if the zoom client binary exists in common locations like /usr/bin/zoom or ~/.zoom/.
    Affected if No Zoom installation found means this CVE does not apply to the environment.
  2. Identify the installed Zoom version
    Run the Zoom client with version information or use package manager queries. For dpkg-based systems: 'dpkg -l | grep zoom' and look for the version number. For RPM-based systems: 'rpm -qa | grep zoom'. You can also try running 'zoom --version' if the binary supports this flag.
    Affected if The command fails to return a version number indicates Zoom may not be properly installed.
  3. Compare installed version against affected range
    Take the version number identified in the previous step (e.g., 5.7.5) and compare it to the affected version range of less than 5.7.10. Parse the full version string (e.g., 5.7.5.321) and compare numerically. Any version below 5.7.10 is affected.
    Affected if The installed version is less than 5.7.10 (for example, 5.7.5, 5.6.0, or any 5.x version below 5.7.10).
  4. Verify authentication is enabled
    This vulnerability requires an authenticated user. Check if Zoom is configured to require authentication by reviewing Zoom meeting settings or checking if the client prompts for login credentials. This is typically the default configuration for enterprise deployments.
    Affected if Zoom is configured to allow unauthenticated access (anonymous users can join meetings without credentials).

The environment is affected if Zoom Desktop Client for Linux is installed with a version less than 5.7.10 and the client is configured to require user authentication, which is the typical default configuration.

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.

dbcve · scoped
Upgrade available Upgrade to 5.7.10 or later
Fixed in 5.7.10
Interim mitigation

Upgrade Zoom Desktop Client for Linux to version 5.17.10 or later. Organizations should deploy the updated client version through their patch management systems and verify successful remediation.

Recommended fix High confidence

Zoom Desktop Client for Linux version 5.7.10 or later

  1. 1. Open the Zoom Desktop Client for Linux
  2. 2. Click on your profile picture or initials in the top-right corner
  3. 3. Select 'Check for Updates' from the dropdown menu
  4. 4. If an update is available, click 'Update' to download and install version 5.7.10 or later
  5. 5. Restart the Zoom client after the update completes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zoom Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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