Process crash via zero-line cursor buffer over-read
Published May 29, 2022 · Updated Aug 3, 2024
Buffer over-read in Vim before 8.2.5037 allows local users to crash the editor when a specially crafted file is opened. The parse_cmd_address function leaves the cursor on line zero after a 0; range, causing utf_ptr2char to read beyond its buffer. User interaction is required to open the file; the demonstrated outcome is termination of the Vim process.
Summary
What happened
Buffer over-read in Vim before 8.2.5037 allows local users to crash the editor when a specially crafted file is opened. The parse_cmd_address function leaves the cursor on line zero after a 0; range, causing utf_ptr2char to read beyond its buffer. User interaction is required to open the file; the demonstrated outcome is termination of the Vim process.
The record
- CVE
- CVE-2022-1927
- Published
- May 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-126, CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 29, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Test_using_zero_in_range 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