Editor crash via aliased buffer-name double free
Published Aug 1, 2024 · Updated Nov 15, 2024
Use-after-free in dialog_changed() in Vim before 9.1.0648 allows local users to crash the editor through a crafted command script. When the save dialog assigns an Untitled name, dialog_changed() clears aliased buffer-name pointers as though each owned separate storage, freeing the same allocation twice. Exploitation requires local low-privileged access and user interaction with a modified unnamed buffer; the demonstrated consequence is editor termination.
Summary
What happened
Use-after-free in dialog_changed() in Vim before 9.1.0648 allows local users to crash the editor through a crafted command script. When the save dialog assigns an Untitled name, dialog_changed() clears aliased buffer-name pointers as though each owned separate storage, freeing the same allocation twice. Exploitation requires local low-privileged access and user interaction with a modified unnamed buffer; the demonstrated consequence is editor termination.
The record
- CVE
- CVE-2024-41965
- Published
- Aug 1, 2024
- Updated
- Nov 15, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, CWE-415, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 15, 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=< 9.1.0648
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
- heap_uaf proof of conceptproof 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