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

> Directory traversal in OpenCV-REST-API allows attackers to read critical secrets and potentially achieve remote code execution.

- **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:** 12 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m6gp-p6w8-32gw

## What is CVE-2021-43494?

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

### Official description

OpenCV-REST-API master branch as of commit 69be158c05d4dd5a4aff38fdc680a162dd6b9e49 is affected by a directory traversal vulnerability. This attack can cause the disclosure of critical secrets stored anywhere on the system and can significantly aid in getting remote code access.

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

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

It affects 1 product.


Products: Codingforentrepreneurs Opencv Rest Api.

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

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

## Is CVE-2021-43494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-43494 is a high-severity path traversal vulnerability in n/a, published on 12 Nov 2021. 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-43494 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-43494/ (Markdown: https://insights.sbomify.com/CVE-2021-43494/index.md)
```

## Sources

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

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