# CVE-2024-24699: Zoom Clients - Business Logic Error

> An authenticated user can exploit a business logic error in Zoom clients to disclose sensitive information via network access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-9x8h-8xf2-qjcv

## What is CVE-2024-24699?

CVE-2024-24699 is a medium-severity vulnerability in Zoom Rooms, published on 13 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Business logic error in some Zoom clients may allow an authenticated user to conduct information disclosure via network access.

## Which versions are affected by CVE-2024-24699?

It affects 4 products.


Products: Zoom Meeting Sdk, Zoom Rooms, Zoom Vdi Windows Meeting Clients, Zoom Zoom.

## How do I fix CVE-2024-24699?

No fix has been published for CVE-2024-24699 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-24699 being exploited?

There is no known exploitation of CVE-2024-24699 in the wild and no public exploit code.

## Other vulnerabilities in Zoom Rooms

- [CVE-2023-34115](https://insights.sbomify.com/CVE-2023-34115/): Memory corruption in Zoom Meeting SDK (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24699 and fix it if it is affected.

What it is: CVE-2024-24699 is a medium-severity vulnerability in Zoom Rooms, published on 13 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-24699 in the wild and no public exploit code.

Affected product: Zoom Rooms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-24699/ (Markdown: https://insights.sbomify.com/CVE-2024-24699/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24699
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24699
- OSV: https://osv.dev/vulnerability/CVE-2024-24699

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-24699/
Summaries are generated and may contain mistakes; the official description above is the record.