Editor crash via null_class member access
Published Mar 11, 2023 · Updated Feb 27, 2025
NULL pointer dereference in Vim before 9.0.1402 allows context-dependent attackers to crash the editor through a crafted Vim9 script. The class_object_index function continues member lookup with a NULL class pointer when null_class.member is evaluated instead of rejecting the incomplete type. Exploitation requires execution of attacker-controlled Vim9 script code, and the demonstrated consequence is interruption of that editor process.
Summary
What happened
NULL pointer dereference in Vim before 9.0.1402 allows context-dependent attackers to crash the editor through a crafted Vim9 script. The class_object_index function continues member lookup with a NULL class pointer when null_class.member is evaluated instead of rejecting the incomplete type. Exploitation requires execution of attacker-controlled Vim9 script code, and the demonstrated consequence is interruption of that editor process.
The record
- CVE
- CVE-2023-1355
- Published
- Mar 11, 2023
- Updated
- Feb 27, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-476, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 27, 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.1402
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
- null_class member-access proof of conceptproof of concept · demonstrated
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