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

> A heap-based buffer overflow in the ok-file-formats library allows attackers to execute arbitrary code or cause denial of service via crafted CSV files.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Dec 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-42fv-xh8h-648w

## What is CVE-2018-20617?

CVE-2018-20617 is a high-severity memory corruption vulnerability in n/a, published on 31 Dec 2018. 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

ok-file-formats through 2018-10-16 has a heap-based buffer overflow in the ok_csv_decode2 function in ok_csv.c.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Ok-File-Formats Project Ok-File-Formats.

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

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

## Is CVE-2018-20617 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28233](https://insights.sbomify.com/CVE-2021-28233/): Memory corruption in n/a (high 8.8)
- [CVE-2018-20616](https://insights.sbomify.com/CVE-2018-20616/): Memory corruption in n/a (high 8.8)
- [CVE-2018-20618](https://insights.sbomify.com/CVE-2018-20618/): Memory corruption in n/a (high 8.8)
- [CVE-2021-41413](https://insights.sbomify.com/CVE-2021-41413/): Memory corruption in n/a (high 7.8)
- [CVE-2021-44335](https://insights.sbomify.com/CVE-2021-44335/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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