Editor crash via mispositioned put end mark
Published Jul 1, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Vim before 9.0 allows attackers to crash the editor by inducing a user to open a crafted file. In do_put() in src/register.c, unused indentation spaces remain in totlen, so an exclusive Visual-mode put places the operation's end mark beyond the line and inc() reads past the allocated buffer. Exploitation requires user interaction with a crafted file and interrupts only the Vim process; published downstream analysis reports no data impact.
Summary
What happened
Heap-based buffer overflow in Vim before 9.0 allows attackers to crash the editor by inducing a user to open a crafted file. In do_put() in src/register.c, unused indentation spaces remain in totlen, so an exclusive Visual-mode put places the operation's end mark beyond the line and inc() reads past the allocated buffer. Exploitation requires user interaction with a crafted file and interrupts only the Vim process; published downstream analysis reports no data impact.
The record
- CVE
- CVE-2022-2264
- Published
- Jul 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 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
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.dev 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