# CVE-2017-6349: Integer overflow in n/a

> An integer overflow in Vim's undo file parser can lead to buffer overflows, potentially allowing arbitrary code execution when opening a malicious file.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-6349, DEBIAN-CVE-2017-6349, GHSA-ppcr-6xhq-q423, UBUNTU-CVE-2017-6349

## What is CVE-2017-6349?

CVE-2017-6349 is a critical vulnerability in Vim Vim, published on 27 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integer overflow at a u_read_undo memory allocation site would occur for vim before patch 8.0.0377, if it does not properly validate values for tree length when reading a corrupted undo file, which may lead to resultant buffer overflows.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2017-6349?

It affects 1 product.


Products: Vim Vim.

## How do I fix CVE-2017-6349?

Apply the vendor's patch.

## Is CVE-2017-6349 being exploited?

There is no known exploitation of CVE-2017-6349 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-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)
- [CVE-2008-3076](https://insights.sbomify.com/CVE-2008-3076/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6349 and fix it if it is affected.

What it is: CVE-2017-6349 is a critical vulnerability in Vim Vim, published on 27 Feb 2017. 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-2017-6349 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-2017-6349/ (Markdown: https://insights.sbomify.com/CVE-2017-6349/index.md)
```

## Sources

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

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