# CVE-2022-23596: Infinite loop in junrar

> A crafted RAR archive triggers an infinite loop in the junrar library, causing denial of service in applications that process untrusted archives.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Feb 2022
- **Updated:** 5 May 2025
- **Also known as:** ECHO-31ea-20fc-ade1, GHSA-m6cj-93v6-cvr5

## What is CVE-2022-23596?

CVE-2022-23596 is a high-severity denial of service vulnerability in n/a, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Junrar is an open source java RAR archive library. In affected versions A carefully crafted RAR archive can trigger an infinite loop while extracting said archive. The impact depends solely on how the application uses the library, and whether files can be provided by malignant users. The problem is patched in 7.4.1. There are no known workarounds and users are advised to upgrade as soon as possible.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

2 open source packages ship an affected version, including com.github.junrar:junrar. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.github.junrar:junrar` | Maven | All versions | 7.4.1 |
| `com.github.junrar:junrar` | Maven | All versions | 7.4.1 |

Products: Junrar Project Junrar.

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

Upgrade com.github.junrar:junrar to 7.4.1 or later.

## Is CVE-2022-23596 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23596 exists.

## Other vulnerabilities in n/a

- [CVE-2026-41245](https://insights.sbomify.com/CVE-2026-41245/): Junrar: Path Traversal (Zip-Slip) via Sibling Directory Name Prefix (medium 5.9)
- [CVE-2026-28208](https://insights.sbomify.com/CVE-2026-28208/): Junrar has arbitrary file write due to backslash path traversal bypass in LocalFolderExtractor on Linux/Unix (medium 5.9)
- [CVE-2018-12418](https://insights.sbomify.com/CVE-2018-12418/): Junrar vulnerable to Infinite Loop (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23596 is a high-severity denial of service vulnerability in n/a, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23596 exists.

Affected packages and fixed versions:
- com.github.junrar:junrar (Maven): affected all versions; fixed in 7.4.1
- com.github.junrar:junrar (Maven): affected all versions; fixed in 7.4.1

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-23596/ (Markdown: https://insights.sbomify.com/CVE-2022-23596/index.md)
```

## Sources

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

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