Editor crash via illegal UTF-8 regexp byte
Published Aug 1, 2022 · Updated Aug 3, 2024
Out-of-bounds read in Vim before 9.0.0104 allows local users to crash the editor with a pattern that starts with an illegal byte. The cstrchr function in src/regexp.c passes that byte through utf_ptr2char and incorrectly treats it as matching a folded character, causing illegal memory access in regexp processing. Exploitation requires user interaction to process the crafted pattern; the documented consequence is a Vim process crash, not a system-wide interruption.
Summary
What happened
Out-of-bounds read in Vim before 9.0.0104 allows local users to crash the editor with a pattern that starts with an illegal byte. The cstrchr function in src/regexp.c passes that byte through utf_ptr2char and incorrectly treats it as matching a folded character, causing illegal memory access in regexp processing. Exploitation requires user interaction to process the crafted pattern; the documented consequence is a Vim process crash, not a system-wide interruption.
The record
- CVE
- CVE-2022-2581
- Published
- Aug 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 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 <9.0.0104
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
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