# CVE-2021-23682: Prototype Pollution

> Prototype pollution in query string parsing allows attackers to modify object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Feb 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v9p9-535w-4285

## What is CVE-2021-23682?

CVE-2021-23682 is a high-severity vulnerability in appwrite/server-ce, published on 16 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects the package litespeed.js before 0.3.12; the package appwrite/server-ce from 0.12.0 and before 0.12.2, before 0.11.1. When parsing the query string in the getJsonFromUrl function, the key that is set in the result object is not properly sanitized leading to a Prototype Pollution vulnerability.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

6 open source packages ship an affected version, including appwrite/server-ce and litespeed.js. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `appwrite/server-ce` | Packagist | All versions | 0.11.1 |
| `appwrite/server-ce` | Packagist | All versions | 0.11.1 |
| `appwrite/server-ce` | Packagist | From 0.12.0 | 0.12.2 |
| `appwrite/server-ce` | Packagist | From 0.12.0 | 0.12.2 |
| `litespeed.js` | npm | All versions | 0.3.12 |
| `litespeed.js` | npm | All versions | 0.3.12 |

Products: Appwrite Appwrite, Litespeed.js Project Litespeed.js.

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

Upgrade appwrite/server-ce to a fixed version for your release line: 0.11.1 or 0.12.2.

## Is CVE-2021-23682 being exploited?

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

## Other vulnerabilities in appwrite/server-ce

- [CVE-2022-2925](https://insights.sbomify.com/CVE-2022-2925/): Cross-site Scripting (XSS) - Stored in appwrite/appwrite (critical 9.0)
- [CVE-2022-25377](https://insights.sbomify.com/CVE-2022-25377/): Appwrite Directory Traversal vulnerability (high 7.5)
- [CVE-2023-27159](https://insights.sbomify.com/CVE-2023-27159/): Appwrite Server-Side Request Forgery vulnerability (high 7.5)
- [CVE-2024-1063](https://insights.sbomify.com/CVE-2024-1063/): Server-side request forgery in Appwrite (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-23682 is a high-severity vulnerability in appwrite/server-ce, published on 16 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-23682 in the wild and no public exploit code.

Affected packages and fixed versions:
- appwrite/server-ce (Packagist): affected all versions; fixed in 0.11.1
- appwrite/server-ce (Packagist): affected all versions; fixed in 0.11.1
- appwrite/server-ce (Packagist): affected from 0.12.0; fixed in 0.12.2
- appwrite/server-ce (Packagist): affected from 0.12.0; fixed in 0.12.2
- litespeed.js (npm): affected all versions; fixed in 0.3.12
- litespeed.js (npm): affected all versions; fixed in 0.3.12

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-23682/ (Markdown: https://insights.sbomify.com/CVE-2021-23682/index.md)
```

## Sources

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

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