Code execution via mis-sized block insertion buffer
Published Jan 18, 2022 · Updated Nov 3, 2025
Heap buffer overflow in Vim before 8.2.4120 allows context-dependent attackers to execute code via crafted block insertion input. The block_insert function in src/ops.c underallocates its new buffer because the size calculation omits copied padding and mishandles an invalid multibyte offset. The trigger requires opening attacker-controlled text and performing Visual-block insertion; memory corruption can crash the editor or run code with the user's privileges.
Summary
What happened
Heap buffer overflow in Vim before 8.2.4120 allows context-dependent attackers to execute code via crafted block insertion input. The block_insert function in src/ops.c underallocates its new buffer because the size calculation omits copied padding and mishandles an invalid multibyte offset. The trigger requires opening attacker-controlled text and performing Visual-block insertion; memory corruption can crash the editor or run code with the user's privileges.
The record
- CVE
- CVE-2022-0261
- Published
- Jan 18, 2022
- Updated
- Nov 3, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2022CVE 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
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
No public exploit references are available in this record.
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