Editor crash via negative command-line insertion position
Published Jun 23, 2022 · Updated Aug 3, 2024
Buffer over-read in Vim before 8.2.5148 allows local users to crash the editor via a crafted command-line expression. In src/ex_getln.c, cmdline_insert_reg resets new_cmdpos to -1 for expression-register insertion but fails to restore it before later command-line processing. The user must interact with a crafted command-line expression; the documented result is invalid memory access that interrupts the editor process.
Summary
What happened
Buffer over-read in Vim before 8.2.5148 allows local users to crash the editor via a crafted command-line expression. In src/ex_getln.c, cmdline_insert_reg resets new_cmdpos to -1 for expression-register insertion but fails to restore it before later command-line processing. The user must interact with a crafted command-line expression; the documented result is invalid memory access that interrupts the editor process.
The record
- CVE
- CVE-2022-2175
- Published
- Jun 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-126, CWE-125
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 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
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
No public exploit references are available in this record.
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