Application crash via invalid for-command line number
Published Sep 3, 2022 · Updated Nov 3, 2025
Use-after-free in Vim before 9.0.0360 allows local users to crash the editor by opening a crafted file containing an invalid :for line number. In do_cmdline() in src/ex_docmd.c, Vim performs breakpoint lookup after the invalid line number leaves no corresponding stored command line, accessing freed line-state memory. The attack requires user interaction with the crafted file, and the upstream reproducer demonstrates an application crash.
Summary
What happened
Use-after-free in Vim before 9.0.0360 allows local users to crash the editor by opening a crafted file containing an invalid :for line number. In do_cmdline() in src/ex_docmd.c, Vim performs breakpoint lookup after the invalid line number leaves no corresponding stored command line, accessing freed line-state memory. The attack requires user interaction with the crafted file, and the upstream reproducer demonstrates an application crash.
The record
- CVE
- CVE-2022-3099
- Published
- Sep 3, 2022
- Updated
- Nov 3, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 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.0360
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
- Test_for_invalid_line_count crash reproducerproof 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