Editor crash via stale define-search pointer
Published May 19, 2022 · Updated Aug 3, 2024
Use-after-free in Vim before 8.2.4979 allows local users to crash the editor during an identifier-based define search. The do_window function retains a pointer into the current buffer line while find_pattern_in_path can flush that line and free its backing memory. The flaw requires local interaction with a buffer, and the publicly demonstrated consequence is an editor crash rather than a security-boundary compromise.
Summary
What happened
Use-after-free in Vim before 8.2.4979 allows local users to crash the editor during an identifier-based define search. The do_window function retains a pointer into the current buffer line while find_pattern_in_path can flush that line and free its backing memory. The flaw requires local interaction with a buffer, and the publicly demonstrated consequence is an editor crash rather than a security-boundary compromise.
The record
- CVE
- CVE-2022-1796
- Published
- May 19, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 19, 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 <8.2.4979
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 CVE-2022-1796 exploit reportproof 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