# CVE-2021-30480: Code injection in n/a

> Remote authenticated attackers within the same organization or accepted contacts can execute arbitrary code without user interaction in Zoom Chat.

- **Severity:** High 8.5 (`CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:L/S:C/UI: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:** 9 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** CVE-2021-34407, GHSA-r6hm-86cv-xhmq

## What is CVE-2021-30480?

CVE-2021-30480 is a high-severity code injection vulnerability in n/a, published on 9 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Zoom Chat through 2021-04-09 on Windows and macOS allows certain remote authenticated attackers to execute arbitrary code without user interaction. An attacker must be within the same organization, or an external party who has been accepted as a contact. NOTE: this is specific to the Zoom Chat software, which is different from the chat feature of the Zoom Meetings and Zoom Video Webinars software.

## Which versions are affected by CVE-2021-30480?

It affects 1 product.


Products: Zoom Chat.

## How do I fix CVE-2021-30480?

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

## Is CVE-2021-30480 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-30480 and fix it if it is affected.

What it is: CVE-2021-30480 is a high-severity code injection vulnerability in n/a, published on 9 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-30480 in the wild and no public exploit code.

Affected product: n/a. 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-2021-30480/ (Markdown: https://insights.sbomify.com/CVE-2021-30480/index.md)
```

## Sources

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

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