Local memory corruption via dummy-buffer navigation
Published Dec 2, 2022 · Updated Apr 23, 2025
Use-after-free in Vim before 9.0.0789 allows local users to trigger memory corruption by opening a crafted file. Vim's do_buffer_ext navigation and split path accepted a dummy buffer and later used freed state; patch 9.0.0789 rejects dummy-buffer navigation. Exploitation requires user interaction to open crafted content and can crash or compromise the editor process.
Summary
What happened
Use-after-free in Vim before 9.0.0789 allows local users to trigger memory corruption by opening a crafted file. Vim's do_buffer_ext navigation and split path accepted a dummy buffer and later used freed state; patch 9.0.0789 rejects dummy-buffer navigation. Exploitation requires user interaction to open crafted content and can crash or compromise the editor process.
The record
- CVE
- CVE-2022-3591
- Published
- Dec 2, 2022
- Updated
- Apr 23, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=unspecified <9.0.0789
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