Editor crash via null-string loop iteration
Published Aug 17, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Vim before 9.0.0220 allows local users to crash or corrupt the editor through a crafted Vim script. The for-loop evaluator calls mb_ptr2len() on a NUL string, while its Latin and DBCS implementations return one instead of zero and advance iteration beyond the allocation. Exploitation requires a user to run an untrusted script that iterates over a null string, producing invalid memory access in the editor process.
Summary
What happened
Heap-based buffer overflow in Vim before 9.0.0220 allows local users to crash or corrupt the editor through a crafted Vim script. The for-loop evaluator calls mb_ptr2len() on a NUL string, while its Latin and DBCS implementations return one instead of zero and advance iteration beyond the allocation. Exploitation requires a user to run an untrusted script that iterates over a null string, producing invalid memory access in the editor process.
The record
- CVE
- CVE-2022-2849
- Published
- Aug 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 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 <9.0.0220
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.
Public exploit references
- huntr.dev Vim null-string loop exploit reportproof of concept · unverified
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