# CVE-2021-3305: Path traversal in n/a

> An attacker can execute arbitrary code by exploiting an untrusted search path vulnerability in the Feishu desktop application.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-38gp-2mrc-f9cj

## What is CVE-2021-3305?

CVE-2021-3305 is a high-severity path traversal vulnerability in n/a, published on 18 Oct 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Beijing Feishu Technology Co., Ltd Feishu v3.40.3 was discovered to contain an untrusted search path vulnerability.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Feishu Feishu.

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

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

## Is CVE-2021-3305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3305 is a high-severity path traversal vulnerability in n/a, published on 18 Oct 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-3305 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-3305/ (Markdown: https://insights.sbomify.com/CVE-2021-3305/index.md)
```

## Sources

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

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