Process memory corruption via virtualedit replacement
Published Sep 17, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Vim before 9.0.0483 allows local users to corrupt process memory through an interactive replace operation. In src/ops.c, op_replace writes a replacement byte over the NUL terminator when virtualedit positions the cursor just after a tab, extending the write beyond the allocated line buffer. Triggering requires user interaction with a crafted editing sequence in virtualedit mode; the upstream reproducer establishes memory corruption rather than a specific code-execution outcome.
Summary
What happened
Heap-based buffer overflow in Vim before 9.0.0483 allows local users to corrupt process memory through an interactive replace operation. In src/ops.c, op_replace writes a replacement byte over the NUL terminator when virtualedit positions the cursor just after a tab, extending the write beyond the allocated line buffer. Triggering requires user interaction with a crafted editing sequence in virtualedit mode; the upstream reproducer establishes memory corruption rather than a specific code-execution outcome.
The record
- CVE
- CVE-2022-3234
- Published
- Sep 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 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 <9.0.0483
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
- Upstream virtualedit replacement regression testproof 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