# CVE-2018-12418: Junrar vulnerable to Infinite Loop

> An attacker can cause a denial of service via an infinite loop in the Junrar library when processing corrupt RAR files.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** ECHO-dcdc-4fd6-a372, GHSA-5xqr-grq4-qwgx

## What is CVE-2018-12418?

CVE-2018-12418 is a medium-severity denial of service vulnerability in n/a, published on 14 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Archive.java in Junrar before 1.0.1, as used in Apache Tika and other products, is affected by a denial of service vulnerability due to an infinite loop when handling corrupt RAR files.

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

## Which versions are affected by CVE-2018-12418?

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 | 1.0.1 |
| `com.github.junrar:junrar` | Maven | All versions | 1.0.1 |

Products: Junrar Project Junrar.

## How do I fix CVE-2018-12418?

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

## Is CVE-2018-12418 being exploited?

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

Public exploit code:

- https://github.com/tafamace/CVE-2018-12418 (github_poc): https://github.com/tafamace/CVE-2018-12418

## Other vulnerabilities in n/a

- [CVE-2022-23596](https://insights.sbomify.com/CVE-2022-23596/): Infinite loop in junrar (high 7.5)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12418 and fix it if it is affected.

What it is: CVE-2018-12418 is a medium-severity denial of service vulnerability in n/a, published on 14 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-12418 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.github.junrar:junrar (Maven): affected all versions; fixed in 1.0.1
- com.github.junrar:junrar (Maven): affected all versions; fixed in 1.0.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-2018-12418/ (Markdown: https://insights.sbomify.com/CVE-2018-12418/index.md)
```

## Sources

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

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