Editor crash via unterminated Lisp indentation scan
Published Jun 19, 2022 · Updated Aug 3, 2024
Heap buffer overflow in Vim before 8.2.5122 allows attackers to crash the editor through a crafted Lisp file opened by a user. The get_lisp_indent function scans a quoted line past its terminating NUL byte instead of stopping before dereferencing the next character. The flaw is reached only when attacker-controlled content is opened or reformatted with Lisp mode and automatic indentation enabled; the grounded consequence is an editor crash.
Summary
What happened
Heap buffer overflow in Vim before 8.2.5122 allows attackers to crash the editor through a crafted Lisp file opened by a user. The get_lisp_indent function scans a quoted line past its terminating NUL byte instead of stopping before dereferencing the next character. The flaw is reached only when attacker-controlled content is opened or reformatted with Lisp mode and automatic indentation enabled; the grounded consequence is an editor crash.
The record
- CVE
- CVE-2022-2125
- Published
- Jun 19, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 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.
Weakness, pattern, technique
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