Editor crash via C-indentation out-of-bounds read
Published May 17, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Vim before 8.2.4968 allows local users to crash the editor through crafted C-indentation input. The skip_string function in src/cindent.c reads p[i] after a digit-scanning loop reaches the terminating NUL, so C-indentation reads past the allocated line buffer. Reaching the flaw requires local execution of Vim and triggering C-indentation; published evidence demonstrates a crash, not code execution or data modification.
Summary
What happened
Heap-based buffer overflow in Vim before 8.2.4968 allows local users to crash the editor through crafted C-indentation input. The skip_string function in src/cindent.c reads p[i] after a digit-scanning loop reaches the terminating NUL, so C-indentation reads past the allocated line buffer. Reaching the flaw requires local execution of Vim and triggering C-indentation; published evidence demonstrates a crash, not code execution or data modification.
The record
- CVE
- CVE-2022-1733
- Published
- May 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, CWE-122
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 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.4968
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