Editor crash via empty spell dictionary
Published Aug 22, 2022 · Updated Aug 3, 2024
NULL pointer dereference in Vim before 9.0.0240 allows local users to crash the editor by running :mkspell on an empty dictionary file. sug_filltree() uses null sl_fbyts and sl_fidxs arrays from an empty word tree without first rejecting that tree. The condition requires an empty .dic file and execution of :mkspell, and the demonstrated consequence is termination of the Vim process.
Summary
What happened
NULL pointer dereference in Vim before 9.0.0240 allows local users to crash the editor by running :mkspell on an empty dictionary file. sug_filltree() uses null sl_fbyts and sl_fidxs arrays from an empty word tree without first rejecting that tree. The condition requires an empty .dic file and execution of :mkspell, and the demonstrated consequence is termination of the Vim process.
The record
- CVE
- CVE-2022-2923
- Published
- Aug 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.0240
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
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