Application crash via invalid Ex-mode pointer
Published Apr 17, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Vim before 8.2.4763 allows context-dependent attackers to crash the editor via a crafted file. In parse_command_modifiers, an empty Visual-range command becomes a literal plus pointer that later code moves backward and treats as writable command-buffer storage. Opening the file and reaching V: in Ex mode is required; the demonstrated consequence is illegal memory access and a process crash.
Summary
What happened
Heap-based buffer overflow in Vim before 8.2.4763 allows context-dependent attackers to crash the editor via a crafted file. In parse_command_modifiers, an empty Visual-range command becomes a literal plus pointer that later code moves backward and treats as writable command-buffer storage. Opening the file and reaching V: in Ex mode is required; the demonstrated consequence is illegal memory access and a process crash.
The record
- CVE
- CVE-2022-1381
- Published
- Apr 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 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 <8.2.4763
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 Ex-mode 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