# CVE-2023-0512: Divide By Zero in vim/vim

> A divide by zero error in Vim allows attackers to cause a denial of service condition.

- **Severity:** High 7.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Jan 2023
- **Updated:** 31 Mar 2025
- **Also known as:** ALPINE-CVE-2023-0512, AZL-13233, BELL-CVE-2023-0512, DEBIAN-CVE-2023-0512, GHSA-whp8-xgvp-xj3v

## What is CVE-2023-0512?

CVE-2023-0512 is a high-severity denial of service vulnerability in Vim Vim, published on 26 Jan 2023. 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

Divide By Zero in GitHub repository vim/vim prior to 9.0.1247.

Weakness: CWE-369 (Divide By Zero)

## Which versions are affected by CVE-2023-0512?

It affects 1 product.


Products: Vim Vim.

## How do I fix CVE-2023-0512?

Upgrade to a fixed version.

## Is CVE-2023-0512 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0512 exists.

## Other vulnerabilities in Vim Vim

- [CVE-2020-20703](https://insights.sbomify.com/CVE-2020-20703/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6349](https://insights.sbomify.com/CVE-2017-6349/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-6350](https://insights.sbomify.com/CVE-2017-6350/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-5953](https://insights.sbomify.com/CVE-2017-5953/): Integer overflow in n/a (critical 9.8)
- [CVE-2008-3075](https://insights.sbomify.com/CVE-2008-3075/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0512 and fix it if it is affected.

What it is: CVE-2023-0512 is a high-severity denial of service vulnerability in Vim Vim, published on 26 Jan 2023. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0512 exists.

Affected product: Vim Vim. 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-2023-0512/ (Markdown: https://insights.sbomify.com/CVE-2023-0512/index.md)
```

## Sources

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

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