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

> Unauthenticated attackers can read arbitrary files on the remote system via a directory traversal vulnerability in the file download endpoint.

- **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:** No
- **Published:** 15 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6ffj-6mvq-rpmh

## What is CVE-2021-35380?

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

### Official description

A Directory Traversal vulnerability exists in Solari di Udine TermTalk Server (TTServer) 3.24.0.2, which lets an unauthenticated malicious user gain access to the files on the remote system by gaining access to the relative path of the file they want to download (http://url:port/file?valore).

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

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

It affects 1 product.


Products: Solari Termtalk Server.

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

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

## Is CVE-2021-35380 being exploited?

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

Public exploit code:

- TermTalk Server 3.24.0.2 - Arbitrary File Read (Unauthenticated) (exploitdb)
- TermTalk Server 3.24.0.2 - Local File Inclusion (nuclei): http/cves/2021/CVE-2021-35380.yaml

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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