CVE-2024-43374
published 2024-08-16CVE-2024-43374: 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…
PriorityP417medium4.7CVSS 3.1
AVLACHPRLUINSUCNINAH
EPSS
0.35%
26.8th percentile
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.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | vim | < vim 2:9.1.0698-1 (forky) | vim 2:9.1.0698-1 (forky) |
| msrc | azl3_vim_9.0.2190-5_on_azure_linux_3.0 | — | — |
| msrc | azl3_vim_9.0.2190-6_on_azure_linux_3.0 | — | — |
| msrc | azure_linux_3.0_arm | — | — |
| msrc | azure_linux_3.0_x64 | — | — |
| msrc | cbl2_vim_9.0.2121-3_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_vim_9.0.2121-5_on_cbl_mariner_2.0 | — | — |
| msrc | cbl_mariner_2.0_arm | — | — |
| msrc | cbl_mariner_2.0_x64 | — | — |
| neovim | neovim | <= 0.10.4 | — |
| vim | vim | < 9.1.0678 | 9.1.0678 |
| vim | vim | >= 0 < 2:9.1.0698-1 | 2:9.1.0698-1 |
| vim | vim | >= 0 < 2:9.1.0698-1 | 2:9.1.0698-1 |
| vim | vim | >= 0 < 2:8.1.2269-1ubuntu5.24 | 2:8.1.2269-1ubuntu5.24 |
| vim | vim | >= 0 < 2:8.2.3995-1ubuntu2.18 | 2:8.2.3995-1ubuntu2.18 |
| vim | vim | >= 0 < 2:9.1.0016-1ubuntu7.2 | 2:9.1.0016-1ubuntu7.2 |
| vim | vim | >= 0 < 2:7.4.052-1ubuntu3.1+esm18 | 2:7.4.052-1ubuntu3.1+esm18 |
| vim | vim | >= 0 < 2:7.4.1689-3ubuntu1.5+esm24 | 2:7.4.1689-3ubuntu1.5+esm24 |
| vim | vim | >= 0 < 2:8.0.1453-1ubuntu1.13+esm9 | 2:8.0.1453-1ubuntu1.13+esm9 |
CVSS provenance
nvdv3.14.7MEDIUMCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.3MEDIUM
vendor_debian4.5LOW
vendor_msrc4.5MEDIUM
vendor_redhat4.5MEDIUM
vendor_ubuntu4.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
vim vulnerabilities
osv·2024-09-05·CVSS 5.3
CVE-2024-41957 [MEDIUM] vim vulnerabilities
vim vulnerabilities
It was discovered that Vim incorrectly handled memory when closing a
window, leading to a double-free vulnerability. If a user was tricked
into opening a specially crafted file, an attacker could crash the
application, leading to a denial of service, or possibly achieve code
execution with user privileges. (CVE-2024-41957)
It was discovered that Vim incorrectly handled memory when adding a new
file to an argument list, leading to a use-after-free. If a user was
tricked into opening a specially crafted file, an attacker could crash
the application, leading to a denial of service. (CVE-2024-43374)
OSV
CVE-2024-43374: The UNIX editor Vim prior to version 9
osv·2024-08-16·CVSS 4.7
CVE-2024-43374 [MEDIUM] CVE-2024-43374: The UNIX editor Vim prior to version 9
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.06
Ubuntu
Vim vulnerabilities
vendor_ubuntu·2024-09-05·CVSS 4.5
CVE-2024-41957 [MEDIUM] Vim vulnerabilities
Title: Vim vulnerabilities
Summary: Several security issues were fixed in Vim.
It was discovered that Vim incorrectly handled memory when closing a
window, leading to a double-free vulnerability. If a user was tricked
into opening a specially crafted file, an attacker could crash the
application, leading to a denial of service, or possibly achieve code
execution with user privileges. (CVE-2024-41957)
It was discovered that Vim incorrectly handled memory when adding a new
file to an argument list, leading to a use-after-free. If a user was
tricked into opening a specially crafted file, an attacker could crash
the application, leading to a denial of service. (CVE-2024-43374)
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
vim: use-after-free in alist_add() in src/arglist.c
vendor_redhat·2024-08-16·CVSS 4.5
CVE-2024-43374 [MEDIUM] CWE-416 vim: use-after-free in alist_add() in src/arglist.c
vim: use-after-free in alist_add() in src/arglist.c
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
Microsoft
Vim heap-use-after-free in src/arglist.c:207
vendor_msrc·2024-08-13·CVSS 4.5
CVE-2024-43374 [MEDIUM] CWE-416 Vim heap-use-after-free in src/arglist.c:207
Vim heap-use-after-free in src/arglist.c:207
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
GitHub_M: GitHub_M
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://learn.micr
Debian
CVE-2024-43374: vim - The UNIX editor Vim prior to version 9.1.0678 has a use-after-free error in argu...
vendor_debian·2024·CVSS 4.5
CVE-2024-43374 [MEDIUM] CVE-2024-43374: vim - The UNIX editor Vim prior to version 9.1.0678 has a use-after-free error in argu...
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.06
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-08-16
Published