Editor crash via malformed statusline value
Published Jan 4, 2023 · Updated Apr 9, 2025
Out-of-bounds read in Vim before 9.0.1143 allows local users to crash the editor through a malformed statusline value. In build_stl_str_hl() in src/buffer.c, the parser advances past the terminating NUL when an unsupported statusline item ends with %0 instead of stopping. Exploitation requires Vim to process and redraw the crafted option in an interactive user session, producing invalid memory access.
Summary
What happened
Out-of-bounds read in Vim before 9.0.1143 allows local users to crash the editor through a malformed statusline value. In build_stl_str_hl() in src/buffer.c, the parser advances past the terminating NUL when an unsupported statusline item ends with %0 instead of stopping. Exploitation requires Vim to process and redraw the crafted option in an interactive user session, producing invalid memory access.
The record
- CVE
- CVE-2023-0049
- Published
- Jan 4, 2023
- Updated
- Apr 9, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 4, 2023CVE publishedPublication date reported by the CVE source.
- Apr 9, 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.1143
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.
Weakness, pattern, technique
Public exploit references
- huntr statusline proof of conceptproof 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