Editor crash via stale argument-list references
Published Aug 15, 2024 · Updated Sep 20, 2024
Use-after-free in Vim before 9.1.0678 allows local users to crash the editor by triggering argument-list autocommands. alist_add() retains window and argument-list references across Buf* autocommands, even though a callback can close the window and free those objects. Exploitation requires unusual Buf* autocommands that wipe a newly created buffer, whether configured manually or supplied by a malicious plugin.
Summary
What happened
Use-after-free in Vim before 9.1.0678 allows local users to crash the editor by triggering argument-list autocommands. alist_add() retains window and argument-list references across Buf* autocommands, even though a callback can close the window and free those objects. Exploitation requires unusual Buf* autocommands that wipe a newly created buffer, whether configured manually or supplied by a malicious plugin.
The record
- CVE
- CVE-2024-43374
- Published
- Aug 15, 2024
- Updated
- Sep 20, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2024CVE publishedPublication date reported by the CVE source.
- Sep 20, 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.0678
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
- heap_use_after_free.tar.gz 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