Memory corruption via oversized Visual range insertion
Published Jul 3, 2022 · Updated Aug 3, 2024
Out-of-bounds write in Vim before 9.0 allows local users to corrupt process memory through a crafted Ex-mode command sequence. The parse_command_modifiers function moves an allocated command in place, then appends the longer '<,'>+ Visual range marker without reserving the extra bytes. Triggering requires Ex mode and command-line window interaction; the write can crash Vim or corrupt its process memory.
Summary
What happened
Out-of-bounds write in Vim before 9.0 allows local users to corrupt process memory through a crafted Ex-mode command sequence. The parse_command_modifiers function moves an allocated command in place, then appends the longer '<,'>+ Visual range marker without reserving the extra bytes. Triggering requires Ex mode and command-line window interaction; the write can crash Vim or corrupt its process memory.
The record
- CVE
- CVE-2022-2288
- Published
- Jul 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 3, 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?
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
- Upstream Ex-mode command-line regression reproducerproof 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