Crash or code execution via invalid cursor column
Published Nov 5, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in Vim before 8.2.3581 allows local users to crash or execute code by opening a crafted file. The gchar_cursor() logic in src/misc1.c can read past the end of a line when the cursor column is invalid, corrupting heap memory. Exploitation requires a victim to open the crafted file, so the practical impact is local and user-triggered rather than remotely reachable.
Summary
What happened
Heap-based buffer overflow in Vim before 8.2.3581 allows local users to crash or execute code by opening a crafted file. The gchar_cursor() logic in src/misc1.c can read past the end of a line when the cursor column is invalid, corrupting heap memory. Exploitation requires a victim to open the crafted file, so the practical impact is local and user-triggered rather than remotely reachable.
The record
- CVE
- CVE-2021-3927
- Published
- Nov 5, 2021
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 5, 2021CVE 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.3581
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