# CVE-2022-2581: Out-of-bounds Read in vim/vim

> An out-of-bounds read in Vim allows attackers to cause a crash or potentially execute arbitrary code via crafted files.

- **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:** 1 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** AZL-10446, CLSA-2022-1660761469, CLSA-2022-1660762683, CLSA-2022-1661174726, DEBIAN-CVE-2022-2581, GHSA-jjq3-r3c2-mg67, UBUNTU-CVE-2022-2581

## What is CVE-2022-2581?

CVE-2022-2581 is a high-severity memory corruption vulnerability in Vim Vim, published on 1 Aug 2022. 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

Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.0104.

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

## Which versions are affected by CVE-2022-2581?

It affects 1 product.


Products: Vim Vim.

## How do I fix CVE-2022-2581?

Upgrade to a fixed version.

## Is CVE-2022-2581 being exploited?

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

## 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-2022-2581 and fix it if it is affected.

What it is: CVE-2022-2581 is a high-severity memory corruption vulnerability in Vim Vim, published on 1 Aug 2022. 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-2022-2581 in the wild and no public exploit code.

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-2022-2581/ (Markdown: https://insights.sbomify.com/CVE-2022-2581/index.md)
```

## Sources

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

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