# CVE-2017-11190: Memory corruption in n/a

> Attackers can cause denial of service via stack-based buffer overflow in unrar-free when debug logging is enabled.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 12 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-11190, GHSA-h73w-w8x7-prqm

## What is CVE-2017-11190?

CVE-2017-11190 is a high-severity memory corruption vulnerability in n/a, published on 12 Jul 2017. 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

unrarlib.c in unrar-free 0.0.1, when _DEBUG_LOG mode is enabled, might allow remote attackers to cause a denial of service (stack-based buffer overflow and application crash) or possibly have unspecified other impact via an RAR archive containing a long filename.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-11190?

It affects 1 product.


Products: Rarzilla Unrar-Free.

## How do I fix CVE-2017-11190?

Apply the vendor's patch.

## Is CVE-2017-11190 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11189](https://insights.sbomify.com/CVE-2017-11189/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11190 and fix it if it is affected.

What it is: CVE-2017-11190 is a high-severity memory corruption vulnerability in n/a, published on 12 Jul 2017. 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-2017-11190 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-2017-11190/ (Markdown: https://insights.sbomify.com/CVE-2017-11190/index.md)
```

## Sources

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

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