Process crash via empty lock command compilation
Published Aug 15, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Vim before 9.0.0211 allows local users to crash the editor by compiling a crafted Vim9 script. The compile_lock_unlock() parser reads p[1] before checking whether an argument follows an empty :lockvar or :unlockvar command, reading past the line buffer. Exploitation requires user interaction to load or compile attacker-controlled script content; the upstream patch documents invalid memory access, while no reliable code-execution consequence is published.
Summary
What happened
Heap-based buffer overflow in Vim before 9.0.0211 allows local users to crash the editor by compiling a crafted Vim9 script. The compile_lock_unlock() parser reads p[1] before checking whether an argument follows an empty :lockvar or :unlockvar command, reading past the line buffer. Exploitation requires user interaction to load or compile attacker-controlled script content; the upstream patch documents invalid memory access, while no reliable code-execution consequence is published.
The record
- CVE
- CVE-2022-2819
- Published
- Aug 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 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.0211
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
- Huntr Vim9 lockvar 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