Editor crash via invalid register contents
Published May 9, 2023 · Updated Jun 23, 2026
NULL pointer dereference in Vim before 9.0.1531 allows local users to crash the editor by running a crafted file in script mode. In get_register() in src/register.c, the copy path accepts a NULL y_current->y_array created by invalid register contents and dereferences it while copying the register. Execution requires user interaction with an untrusted script-input file; the supported consequence is termination of the Vim process, not data disclosure or code execution.
Summary
What happened
NULL pointer dereference in Vim before 9.0.1531 allows local users to crash the editor by running a crafted file in script mode. In get_register() in src/register.c, the copy path accepts a NULL y_current->y_array created by invalid register contents and dereferences it while copying the register. Execution requires user interaction with an untrusted script-input file; the supported consequence is termination of the Vim process, not data disclosure or code execution.
The record
- CVE
- CVE-2023-2609
- Published
- May 9, 2023
- Updated
- Jun 23, 2026
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record 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.1531
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.dev proof-of-concept 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