# CVE-2020-20335: Integer overflow in n/a

> A remote attacker can cause a denial of service in the Kilo text editor via an integer overflow in the editorUpdateRow function.

- **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:** No
- **Published:** 20 Jun 2023
- **Updated:** 10 Dec 2024
- **Also known as:** GHSA-w2mw-92v8-xh4h

## What is CVE-2020-20335?

CVE-2020-20335 is a high-severity vulnerability in n/a, published on 20 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow vulnerability in Antirez Kilo before commit 7709a04ae8520c5b04d261616098cebf742f5a23 allows a remote attacker to cause a denial of service via the editorUpdateRow function in kilo.c.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2020-20335?

It affects 1 product.


Products: Kilo Project Kilo.

## How do I fix CVE-2020-20335?

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

## Is CVE-2020-20335 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16096](https://insights.sbomify.com/CVE-2019-16096/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-20335 and fix it if it is affected.

What it is: CVE-2020-20335 is a high-severity vulnerability in n/a, published on 20 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-20335 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-2020-20335/ (Markdown: https://insights.sbomify.com/CVE-2020-20335/index.md)
```

## Sources

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

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