Editor crash via premature ModeChanged dispatch
Published Nov 19, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in Vim before 8.2.3610 allows context-dependent attackers to crash the editor via ModeChanged. The n_start_visual_mode function triggers ModeChanged before completing Visual-mode state setup, allowing a recursive autocommand to use inconsistent heap-backed editor state. Exploitation requires a ModeChanged autocommand to run during entry into Visual mode; the upstream regression test demonstrates an editor-process crash.
Summary
What happened
Heap-based buffer overflow in Vim before 8.2.3610 allows context-dependent attackers to crash the editor via ModeChanged. The n_start_visual_mode function triggers ModeChanged before completing Visual-mode state setup, allowing a recursive autocommand to use inconsistent heap-backed editor state. Exploitation requires a ModeChanged autocommand to run during entry into Visual mode; the upstream regression test demonstrates an editor-process crash.
The record
- CVE
- CVE-2021-3968
- Published
- Nov 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, CWE-122
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 19, 2021CVE 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.3610
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 ModeChanged crash 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