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

> A registered user can exploit path traversal in attachment downloads to read arbitrary server files, leading to information disclosure.

- **Severity:** High 7.7 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9v7f-rj28-9x3v

## What is CVE-2021-41714?

CVE-2021-41714 is a high-severity path traversal vulnerability in n/a, published on 23 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Tipask < 3.5.9, path parameters entered by the user are not validated when downloading attachments, a registered user can download arbitrary files on the Tipask server such as .env, /etc/passwd, laravel.log, causing infomation leakage.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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

It affects 1 product.


Products: Tipask Tipask.

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

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

## Is CVE-2021-41714 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41714 is a high-severity path traversal vulnerability in n/a, published on 23 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41714 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-41714/ (Markdown: https://insights.sbomify.com/CVE-2021-41714/index.md)
```

## Sources

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

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