Editor crash via negative virtual-edit spacing
Published Mar 4, 2023 · Updated Nov 3, 2025
Incorrect buffer-size calculation in Vim before 9.0.1378 allows context-dependent attackers to crash the editor via a crafted file. The op_yank function in src/register.c permits the computed startspaces value to become negative during virtual editing, leading to illegal memory access. Exploitation requires a user to process crafted content, and the reported consequences include an editor crash and memory corruption.
Summary
What happened
Incorrect buffer-size calculation in Vim before 9.0.1378 allows context-dependent attackers to crash the editor via a crafted file. The op_yank function in src/register.c permits the computed startspaces value to become negative during virtual editing, leading to illegal memory access. Exploitation requires a user to process crafted content, and the reported consequences include an editor crash and memory corruption.
The record
- CVE
- CVE-2023-1175
- Published
- Mar 4, 2023
- Updated
- Nov 3, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-131, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2023CVE 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 <9.0.1378
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.
Public exploit references
- huntr proof-of-concept exploitproof 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