Editor crash via cursor underflow during folding
Published Jan 13, 2023 · Updated Apr 7, 2025
Heap-based buffer overflow in Vim before 9.0.1189 allows local users to crash the editor by triggering the L command with folding enabled. The nv_scroll function lets hasFolding reset the cursor to the top line and then unconditionally decrements it to line zero, causing undo state to use line number minus one and access invalid heap memory. Reaching the flaw requires local interaction with a folded buffer; the demonstrated consequence is an editor crash, not a network service outage.
Summary
What happened
Heap-based buffer overflow in Vim before 9.0.1189 allows local users to crash the editor by triggering the L command with folding enabled. The nv_scroll function lets hasFolding reset the cursor to the top line and then unconditionally decrements it to line zero, causing undo state to use line number minus one and access invalid heap memory. Reaching the flaw requires local interaction with a folded buffer; the demonstrated consequence is an editor crash, not a network service outage.
The record
- CVE
- CVE-2023-0288
- Published
- Jan 13, 2023
- Updated
- Apr 7, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2023CVE publishedPublication date reported by the CVE source.
- Apr 7, 2025Record 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.1189
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
- huntr folding and L-command proof of conceptproof 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