Editor crash via reentrant FileType autocommand
Published Oct 26, 2022 · Updated Apr 15, 2025
Use-after-free in Vim before 9.0.0805 allows context-dependent attackers to crash the editor through a FileType autocommand. The qf_update_buffer function invokes FileType autocommands while filling a quickfix or location-list buffer without marking the list busy, allowing callback-driven list replacement to free memory that the update still uses. Triggering requires a FileType autocommand that mutates the active list; the documented consequence is a CLI process crash.
Summary
What happened
Use-after-free in Vim before 9.0.0805 allows context-dependent attackers to crash the editor through a FileType autocommand. The qf_update_buffer function invokes FileType autocommands while filling a quickfix or location-list buffer without marking the list busy, allowing callback-driven list replacement to free memory that the update still uses. Triggering requires a FileType autocommand that mutates the active list; the documented consequence is a CLI process crash.
The record
- CVE
- CVE-2022-3705
- Published
- Oct 26, 2022
- Updated
- Apr 15, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, CWE-119
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=n/a
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.
Weakness, pattern, technique
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