Editor crash via invalid post-format cursor
Published May 25, 2022 · Updated Aug 3, 2024
Out-of-bounds read in Vim before patch 8.2.5013 allows context-dependent attackers to crash the editor during text formatting. In op_format, formatting can shorten a line after the saved cursor is restored, leaving its column beyond the new line end without calling check_cursor. Exploitation requires user interaction with a crafted editing sequence; the published regression test exposes the invalid read under Valgrind.
Summary
What happened
Out-of-bounds read in Vim before patch 8.2.5013 allows context-dependent attackers to crash the editor during text formatting. In op_format, formatting can shorten a line after the saved cursor is restored, leaving its column beyond the new line end without calling check_cursor. Exploitation requires user interaction with a crafted editing sequence; the published regression test exposes the invalid read under Valgrind.
The record
- CVE
- CVE-2022-1851
- Published
- May 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 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
- Test_correct_cursor_position regression triggerproof 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