# CVE-2024-43374: Vim heap-use-after-free in src/arglist.c:207

> A use-after-free in Vim's argument list handling allows a crash if malicious autocommands are triggered, requiring user interaction or malicious plugins.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **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:** 15 Aug 2024
- **Updated:** 20 Sep 2024
- **Also known as:** ALPINE-CVE-2024-43374, AZL-47817, AZL-47832, BELL-CVE-2024-43374, CLSA-2024-1730133086, DEBIAN-CVE-2024-43374, ECHO-d1ca-6d1a-5e4d, GHSA-2w8m-443v-cgvw, OESA-2024-2026, ROOT-OS-ALPINE-318-CVE-2024-43374, ROOT-OS-ALPINE-319-CVE-2024-43374, UBUNTU-CVE-2024-43374

## What is CVE-2024-43374?

CVE-2024-43374 is a medium-severity use after free vulnerability in Netapp Bootstrap Os, published on 15 Aug 2024. 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

The UNIX editor Vim prior to version 9.1.0678 has a use-after-free error in argument list handling. When adding a new file to the argument list, this triggers `Buf*` autocommands. If in such an autocommand the buffer that was just opened is closed (including the window where it is shown), this causes the window structure to be freed which contains a reference to the argument list that we are actually modifying. Once the autocommands are completed, the references to the window and argument list are no longer valid and as such cause an use-after-free. Impact is low since the user must either intentionally add some unusual autocommands that wipe a buffer during creation (either manually or by sourcing a malicious plugin), but it will crash Vim. The issue has been fixed as of Vim patch v9.1.0678.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-43374?

It affects 3 products.


Products: Neovim Neovim, Netapp Bootstrap Os, Vim Vim.

## How do I fix CVE-2024-43374?

Upgrade to a fixed version.

## Is CVE-2024-43374 being exploited?

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

## Other vulnerabilities in Netapp Bootstrap Os

- [CVE-2019-12735](https://insights.sbomify.com/CVE-2019-12735/): Command injection in n/a (high 8.6)
- [CVE-2022-3591](https://insights.sbomify.com/CVE-2022-3591/): Use After Free in vim/vim (high 7.8)
- [CVE-2026-45130](https://insights.sbomify.com/CVE-2026-45130/): Vim: Heap Buffer Overflow in spell file loading (medium 6.6)
- [CVE-2026-25749](https://insights.sbomify.com/CVE-2026-25749/): Heap Overflow in Vim (medium 6.6)
- [CVE-2025-22134](https://insights.sbomify.com/CVE-2025-22134/): heap-buffer-overflow with visual mode in Vim < 9.1.1003 (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-43374 and fix it if it is affected.

What it is: CVE-2024-43374 is a medium-severity use after free vulnerability in Netapp Bootstrap Os, published on 15 Aug 2024. 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-2024-43374 in the wild and no public exploit code.

Affected product: Netapp Bootstrap Os. 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-2024-43374/ (Markdown: https://insights.sbomify.com/CVE-2024-43374/index.md)
```

## Sources

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

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