CVE-2024-43374 [Medium] | Use-After-Free in Bootstrap Os

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.08%	0.35%	+0.27%
2	2025-09-23	0.02%	0.08%	+0.06%
3	2025-04-15	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.08%

0.35%

+0.27%

2025-09-23

0.02%

0.08%

+0.06%

2025-04-15

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.0	3.4	[email protected]
4.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.0	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.0

3.4

[email protected]

4.7

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.0

3.6

[email protected]

OS Trackers for CVE-2024-43374

vendor	priority	summary	link
`alpine`	—	CVE-2024-43374: 1 source package rows (vim); 200 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 4, open 196.	https://security.alpinelinux.org/vuln/CVE-2024-43374
`debian`	unimportant	CVE-2024-43374 unimportant priority: Debian including 1 source packages (vim), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2.	https://security-tracker.debian.org/tracker/CVE-2024-43374
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2024-43374
`suse`	medium	CVE-2024-43374 severity moderate: SUSE including 270 source package names (1.5.0:vim-data-common-9.1.0836-150500.20.15.1, 1.5.0:vim-small-9.1.0836-150500.20.15.1, …), 764 product×package rows across 226 product lines (Container suse/hpc/warewulf4-x86_64/sle-hpc-node, Container suse/manager/5.0/x86_64/server, … (226 product lines)): Fixed 429, Known Affected 231, Known Not Affected 104.	https://www.suse.com/security/cve/CVE-2024-43374/
`ubuntu`	medium	CVE-2024-43374 medium priority: Ubuntu including 1 source packages (vim), 7 status rows across 7 suites (bionic, focal, jammy, noble, trusty, upstream, xenial): released 7.	https://ubuntu.com/security/CVE-2024-43374

Affected software / configurations for CVE-2024-43374

Vendor	Product	Version	Raw CPE
netapp	bootstrap_os	—	cpe:2.3:o:netapp:bootstrap_os:-:::::::*
neovim	neovim	<= 0.10.4	cpe:2.3:a:neovim:neovim::::::::
vim	vim	< 9.1.0678	cpe:2.3:a:vim:vim::::::::

References for CVE-2024-43374

URL	Tags
https://github.com/vim/vim/commit/0a6e57b09bc8c76691b367a5babfb79b31b770e8	Patch
https://github.com/vim/vim/security/advisories/GHSA-2w8m-443v-cgvw	Vendor Advisory
http://www.openwall.com/lists/oss-security/2024/08/15/6	Mailing List Third Party Advisory
https://security.netapp.com/advisory/ntap-20240920-0004/	Third Party Advisory

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2024-43374

Common vulnerability scoring system (CVSS) metrics for CVE-2024-43374

Weakness enumeration for CVE-2024-43374

OS Trackers for CVE-2024-43374

Affected software / configurations for CVE-2024-43374

References for CVE-2024-43374