# CVE-2022-21675: Bytecode Viewer v2.10.x Zip Slip

> Attackers can achieve remote code execution by exploiting a Zip Slip vulnerability in Bytecode Viewer via crafted archives.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H`)
- **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:** 12 Jan 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-3wq9-j4fc-4wmc

## What is CVE-2022-21675?

CVE-2022-21675 is a critical path traversal vulnerability in Konloch bytecode-viewer, published on 12 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Bytecode Viewer (BCV) is a Java/Android reverse engineering suite. Versions of the package prior to 2.11.0 are vulnerable to Arbitrary File Write via Archive Extraction (AKA "Zip Slip"). The vulnerability is exploited using a specially crafted archive that holds directory traversal filenames (e.g. ../../evil.exe). The Zip Slip vulnerability can affect numerous archive formats, including zip, jar, tar, war, cpio, apk, rar and 7z. The attacker can then overwrite executable files and either invoke them remotely or wait for the system or user to call them, thus achieving remote command execution on the victim’s machine. The impact of a Zip Slip vulnerability would allow an attacker to create or overwrite existing files on the filesystem. In the context of a web application, a web shell could be placed within the application directory to achieve code execution. All users should upgrade to BCV v2.11.0 when possible to receive a patch. There are no recommended workarounds aside from upgrading.

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

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

It affects 1 product.


Products: Bytecode Viewer Project Bytecode Viewer.

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

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

## Is CVE-2022-21675 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21675 is a critical path traversal vulnerability in Konloch bytecode-viewer, published on 12 Jan 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-2022-21675 in the wild and no public exploit code.

Affected product: Konloch bytecode-viewer. 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-21675/ (Markdown: https://insights.sbomify.com/CVE-2022-21675/index.md)
```

## Sources

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

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