Crash via autocommand-triggered buffer use-after-free
Published Oct 11, 2023 · Updated Feb 13, 2025
Use-after-free in Vim before 9.0.2010 allows local users to crash the editor by opening a crafted file that triggers buffer checks. The buf_contents_changed() routine rereads a file without blocking autocommands, which can wipe a buffer while the routine still uses it. Exploitation requires user interaction with a crafted file; the public regression case demonstrates process termination, while code execution is not established.
Summary
What happened
Use-after-free in Vim before 9.0.2010 allows local users to crash the editor by opening a crafted file that triggers buffer checks. The buf_contents_changed() routine rereads a file without blocking autocommands, which can wipe a buffer while the routine still uses it. Exploitation requires user interaction with a crafted file; the public regression case demonstrates process termination, while code execution is not established.
The record
- CVE
- CVE-2023-5535
- Published
- Oct 11, 2023
- Updated
- Feb 13, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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 <v9.0.2010
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
- editing_arg_idx_POC_1 Vim crash reproducerproof 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