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

> Attackers can exploit unsanitized deeplinks to write files to the app's data directory, enabling arbitrary code execution via dynamic library loading.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2023
- **Updated:** 3 Feb 2025

## What is CVE-2022-47757?

CVE-2022-47757 is a critical path traversal vulnerability in n/a, published on 4 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In imo.im 2022.11.1051, a path traversal vulnerability delivered via an unsanitized deeplink can force the application to write a file into the application's data directory. This may allow an attacker to save a shared library under a special directory which the app uses to dynamically load modules. Loading the library can lead to arbitrary code execution.

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

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

It affects 1 product.


Products: Imo Imo.

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

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

## Is CVE-2022-47757 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47757 is a critical path traversal vulnerability in n/a, published on 4 May 2023. 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-47757 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-47757/ (Markdown: https://insights.sbomify.com/CVE-2022-47757/index.md)
```

## Sources

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

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