Editor crash via stale location-list pointers
Published Aug 28, 2022 · Updated Aug 3, 2024
Use-after-free in Vim before 9.0.0286 allows context-dependent attackers to crash the editor through a crafted file opened by a user. In src/quickfix.c, the jump path retains stale quickfix or location-list pointers after a BufEnter autocommand replaces the location list. Exploitation requires a user to open the crafted file locally; the demonstrated consequence is an editor crash, and no remote service is exposed.
Summary
What happened
Use-after-free in Vim before 9.0.0286 allows context-dependent attackers to crash the editor through a crafted file opened by a user. In src/quickfix.c, the jump path retains stale quickfix or location-list pointers after a BufEnter autocommand replaces the location list. Exploitation requires a user to open the crafted file locally; the demonstrated consequence is an editor crash, and no remote service is exposed.
The record
- CVE
- CVE-2022-3016
- Published
- Aug 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 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.0286
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 CVE-2022-3016 proof of conceptproof 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