# CVE-2018-18059: Memory corruption in n/a

> A buffer over-read in the RAR parser allows attackers to cause a denial of service by tricking users into opening malicious files.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wg44-x9gh-5r62

## What is CVE-2018-18059?

CVE-2018-18059 is a medium-severity memory corruption vulnerability in n/a, published on 24 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Bitdefender Engines before 7.76675. A vulnerability has been discovered in the rar.xmd parser that results from a lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. Paired with other vulnerabilities, this can result in denial-of-service. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Bitdefender Scan Engines.

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

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

## Is CVE-2018-18059 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18058](https://insights.sbomify.com/CVE-2018-18058/): Denial of service in n/a (medium 5.3)
- [CVE-2018-18060](https://insights.sbomify.com/CVE-2018-18060/): Denial of service in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18059 is a medium-severity memory corruption vulnerability in n/a, published on 24 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-18059 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-2018-18059/ (Markdown: https://insights.sbomify.com/CVE-2018-18059/index.md)
```

## Sources

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

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