# CVE-2022-25377: Appwrite Directory Traversal vulnerability

> Remote attackers can read arbitrary local files via directory traversal in the ACME-challenge endpoint if the certificate storage path exists.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Feb 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-wfm3-gq9h-mrjm

## What is CVE-2022-25377?

CVE-2022-25377 is a high-severity path traversal vulnerability in n/a, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ACME-challenge endpoint in Appwrite 0.5.0 through 0.12.x before 0.12.2 allows remote attackers to read arbitrary local files via ../ directory traversal. In order to be vulnerable, APP_STORAGE_CERTIFICATES/.well-known/acme-challenge must exist on disk. (This pathname is automatically created if the user chooses to install Let's Encrypt certificates via Appwrite.)

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-25377?

2 open source packages ship an affected version, including appwrite/server-ce. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `appwrite/server-ce` | Packagist | From 0.5.0 | 0.12.2 |
| `appwrite/server-ce` | Packagist | From 0.5.0 | 0.12.2 |

Products: Appwrite Appwrite.

## How do I fix CVE-2022-25377?

Upgrade appwrite/server-ce to 0.12.2 or later.

## Is CVE-2022-25377 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-2925](https://insights.sbomify.com/CVE-2022-2925/): Cross-site Scripting (XSS) - Stored in appwrite/appwrite (critical 9.0)
- [CVE-2023-27159](https://insights.sbomify.com/CVE-2023-27159/): Appwrite Server-Side Request Forgery vulnerability (high 7.5)
- [CVE-2021-23682](https://insights.sbomify.com/CVE-2021-23682/): Prototype Pollution (high 7.3)
- [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-2022-25377 and fix it if it is affected.

What it is: CVE-2022-25377 is a high-severity path traversal vulnerability in n/a, published on 22 Feb 2024. 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-2022-25377 exists.

Affected packages and fixed versions:
- appwrite/server-ce (Packagist): affected from 0.5.0; fixed in 0.12.2
- appwrite/server-ce (Packagist): affected from 0.5.0; fixed in 0.12.2

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

## Sources

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

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