# CVE-2022-27906: Path traversal in n/a

> An attacker with a valid Odette ID can upload files outside the intended directory via path traversal in Mendelson OFTP2.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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:** 25 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fxrm-2v78-3qr9

## What is CVE-2022-27906?

CVE-2022-27906 is a medium-severity path traversal vulnerability in n/a, published on 25 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mendelson OFTP2 before 1.1 b43 is affected by directory traversal. To access the vulnerable code path, the attacker has to know one of the configured Odette IDs of the OFTP2 server. An attacker can upload files to the server outside of the intended upload directory.

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

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

It affects 1 product.


Products: Mendelson Oftp2.

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

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

## Is CVE-2022-27906 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27906 and fix it if it is affected.

What it is: CVE-2022-27906 is a medium-severity path traversal vulnerability in n/a, published on 25 Mar 2022. 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-2022-27906 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-2022-27906/ (Markdown: https://insights.sbomify.com/CVE-2022-27906/index.md)
```

## Sources

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

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