Skip to content
Noroxi
CVE-2024-43374· NVD / CVE Program· CNA GitHub_M

Vim heap-use-after-free in src/arglist.c:207

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Azure Linux 3.0 ARM 9.0.2190-5; Azure Linux 3.0 x64 9.0.2190-5; CBL Mariner 2.0 ARM 9.0.2121-3.

Low priority for now. Upgrade to Azure Linux 3.0 ARM 9.0.2190-5; Azure Linux 3.0 x64 9.0.2190-5; CBL Mariner 2.0 ARM 9.0.2121-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Aug 15, 2024
Updated
Jun 17, 2026
EPSS
0.3% · 27th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.7
CNA · GitHub_M
4.5
0.2 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-43374

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
vimvim
netappbootstrap os
netapphci compute node
neovimneovim

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • neovim neovimup to 0.10.4 inclusive
  • netapp bootstrap osall versions
  • vim vimbefore 9.1.0678

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • vim vim

    • < 9.1.0678affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.20vimbefore 9.1.0678-r09.1.0678-r0
Debian:12vimfrom 0—
Debian:13vimbefore 2:9.1.0698-12:9.1.0698-1
openSUSE:Leap Micro 5.5vimbefore 9.1.0836-150500.20.15.19.1.0836-150500.20.15.1
SUSE:Linux Enterprise Micro 5.5vimbefore 9.1.0836-150500.20.15.19.1.0836-150500.20.15.1
SUSE:Linux Enterprise Server 12 SP5-LTSSvimbefore 9.1.0836-17.38.19.1.0836-17.38.1
SUSE:Linux Micro 6.0vimbefore 9.1.1101-1.19.1.1101-1.1

Same product

vim: all records

Other highest-scoring records for the same primary product.

  • CVE-2008-2712Vim 7.1.314, 6.4, and other versions allows user-assisted remote attackers to execute arbitrary commands via Vim scripts that do not properl
    42Plan
  • CVE-2022-0318Heap-based Buffer Overflow in vim/vim
    40Plan
  • CVE-2019-12735getchar.c in Vim before 8.1.1365 and Neovim before 0.3.6 allows remote attackers to execute arbitrary OS commands via the :source! command i
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-41957Aug 1, 2024 · Vim double free in src/alloc.c:616
    21Monitor
  • ← EarlierCVE-2024-41965Aug 1, 2024 · Vim < v9.1.0648 has a double-free in dialog_changed()
    16Monitor
  • Later →CVE-2024-43790Aug 22, 2024 · heap-buffer-overflow in do_search() in Vim < 9.1.0689
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Azure Linux 3.0 ARM9.0.2190-5 · vimMicrosoft (MSRC)
Azure Linux 3.0 x649.0.2190-5 · vimMicrosoft (MSRC)
CBL Mariner 2.0 ARM9.0.2121-3 · vimMicrosoft (MSRC)
CBL Mariner 2.0 x649.0.2121-3 · vimMicrosoft (MSRC)
alpine:vim9.1.0678-r0 · Alpine:v3.20Package registry (OSV)
debian:vim2:9.1.0698-1 · Debian:13Package registry (OSV)
opensuse:vim9.1.0836-150500.20.15.1 · openSUSE:Leap Micro 5.5Package registry (OSV)
suse:vim9.1.0836-150500.20.15.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-5535309 days apartUse After Free in vim/vim
    31Monitor
  • CVE-2023-4733346 days apartUse After Free in vim/vim
    31Monitor
  • CVE-2023-4750346 days apartUse After Free in vim/vim
    31Monitor
  • CVE-2023-4752346 days apartUse After Free in vim/vim
    31Monitor
  • CVE-2025-55157361 days apartVim heap use-after-free vulnerability when processing recursive tuple data types
    27Monitor
  • CVE-2024-4781453 days apartuse-after-free when closing buffers in Vim
    18Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records