Editor crash via miscomputed sourced-line length
Published May 17, 2022 · Updated Aug 3, 2024
Buffer over-read in Vim before 8.2.4974 allows local users to crash the editor by sourcing a crafted script with a long multibyte line. In get_one_sourceline() in src/scriptfile.c, the buffer-input path increments ga.ga_len after appending a NUL byte, then calculates the line length with STRLEN from beyond that terminator. Exploitation requires attacker-controlled Vim script content to be processed by :source; the demonstrated consequence is an editor crash, not code execution.
Summary
What happened
Buffer over-read in Vim before 8.2.4974 allows local users to crash the editor by sourcing a crafted script with a long multibyte line. In get_one_sourceline() in src/scriptfile.c, the buffer-input path increments ga.ga_len after appending a NUL byte, then calculates the line length with STRLEN from beyond that terminator. Exploitation requires attacker-controlled Vim script content to be processed by :source; the demonstrated consequence is an editor crash, not code execution.
The record
- CVE
- CVE-2022-1769
- Published
- May 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-126, CWE-125
- Attack vector
- local
- Privileges
- authenticated
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.4974
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