# CVE-2021-22911: Code injection in Rocket.Chat server

> Unauthenticated attackers can exploit improper input sanitization in Rocket.Chat server to achieve remote code execution via NoSQL injection.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fj2w-2856-965h

## What is CVE-2021-22911?

CVE-2021-22911 is a critical code injection vulnerability in Rocket.chat Rocket.chat, published on 27 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A improper input sanitization vulnerability exists in Rocket.Chat server 3.11, 3.12 & 3.13 that could lead to unauthenticated NoSQL injection, resulting potentially in RCE.

Weakness: CWE-75 (Failure to Sanitize Special Elements into a Different Plane)

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

It affects 1 product.


Products: Rocket.chat Rocket.chat.

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

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

## Is CVE-2021-22911 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-22911 exists.

Public exploit code:

- Pre-Auth Blind NoSQL Injection leading to Remote Code Execution in Rocket Chat 3.12.1 (github_poc): https://github.com/CsEnox/CVE-2021-22911
- Full unauthenticated RCE proof of concept for Rocket.Chat 3.12.1 CVE-2021-22911 (github_poc): https://github.com/optionalCTF/Rocket.Chat-Automated-Account-Takeover-RCE-CVE-2021-22911
- https://github.com/Faridi-m/CVE-2021-22911-RocketChat (github_poc): https://github.com/Faridi-m/CVE-2021-22911-RocketChat
- CVE-2021-22911 Rocket.Chat NoSQL Injection RCE Exploit - Educational Purpose (github_poc): https://github.com/roshanrajbanshi/rocketcat-cve-2021-22911-exploit
- Rocket.Chat 3.12.1 - NoSQL Injection (Unauthenticated) (exploitdb)
- Rocket.Chat 3.12.1 - NoSQL Injection to RCE (Unauthenticated) (2) (exploitdb)

## Other vulnerabilities in Rocket.chat Rocket.chat

- [CVE-2026-58066](https://insights.sbomify.com/CVE-2026-58066/): Auth bypass in Rocket.Chat (critical 9.8)
- [CVE-2026-29198](https://insights.sbomify.com/CVE-2026-29198/): SQL injection in Rocket.Chat (critical 9.8)
- [CVE-2023-28316](https://insights.sbomify.com/CVE-2023-28316/): Security feature bypass in Rocket.Chat (critical 9.8)
- [CVE-2022-44567](https://insights.sbomify.com/CVE-2022-44567/): Command injection in Rocket.chat - Electron Desktop (critical 9.8)
- [CVE-2021-22910](https://insights.sbomify.com/CVE-2021-22910/): Code injection in Rocket.Chat server (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22911 is a critical code injection vulnerability in Rocket.chat Rocket.chat, published on 27 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-22911 exists.

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

## Sources

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

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