Editor crash via unchecked finally stack search
Published Sep 25, 2022 · Updated May 22, 2025
Stack-based buffer overflow in Vim before 9.0.0577 allows attackers to crash the editor after a user opens a crafted file. The ex_finally() handler in src/ex_eval.c searches backward through the conditional-stack array for CSF_TRY without first confirming that such an entry exists. User interaction is required, and the resulting underflow corrupts stack memory and interrupts the local editing process.
Summary
What happened
Stack-based buffer overflow in Vim before 9.0.0577 allows attackers to crash the editor after a user opens a crafted file. The ex_finally() handler in src/ex_eval.c searches backward through the conditional-stack array for CSF_TRY without first confirming that such an entry exists. User interaction is required, and the resulting underflow corrupts stack memory and interrupts the local editing process.
The record
- CVE
- CVE-2022-3296
- Published
- Sep 25, 2022
- Updated
- May 22, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, CWE-121, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 25, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 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.0577
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 proof of concept for unexpected :finallyproof 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