Process crash via unbounded help argument copy
Published Dec 1, 2021 · Updated Nov 3, 2025
Heap-based buffer overflow in Vim before 8.2.3669 allows local users to crash the editor by supplying a long help argument. In find_help_tags() in src/help.c, consecutive STRCPY calls append the argument to a fixed IOSIZE buffer without enforcing its length. Triggering the overflow requires local execution of Vim's help command with a crafted argument; the demonstrated consequence is a process crash.
Summary
What happened
Heap-based buffer overflow in Vim before 8.2.3669 allows local users to crash the editor by supplying a long help argument. In find_help_tags() in src/help.c, consecutive STRCPY calls append the argument to a fixed IOSIZE buffer without enforcing its length. Triggering the overflow requires local execution of Vim's help command with a crafted argument; the demonstrated consequence is a process crash.
The record
- CVE
- CVE-2021-4019
- Published
- Dec 1, 2021
- Updated
- Nov 3, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2021CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <8.2.3669
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr.dev long-help-argument exploit reportproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo