Editor crash via stale visual-mode buffer position
Published Jan 13, 2025 · Updated Mar 14, 2025
Heap-based buffer overflow in Vim before 9.1.1003 allows local users to crash the editor by invoking :all while visual mode remains active. The do_arg_all path retains visual-mode cursor and selection positions across buffer changes, after which gchar_pos and charwise_block_prep can address beyond the new line boundary. Exploitation requires a local Vim session, active visual mode, and the :all command; the published reproducer reads outside heap bounds and aborts the process.
Summary
What happened
Heap-based buffer overflow in Vim before 9.1.1003 allows local users to crash the editor by invoking :all while visual mode remains active. The do_arg_all path retains visual-mode cursor and selection positions across buffer changes, after which gchar_pos and charwise_block_prep can address beyond the new line boundary. Exploitation requires a local Vim session, active visual mode, and the :all command; the published reproducer reads outside heap bounds and aborts the process.
The record
- CVE
- CVE-2025-22134
- Published
- Jan 13, 2025
- Updated
- Mar 14, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2025CVE publishedPublication date reported by the CVE source.
- Mar 14, 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=< v9.1.1003
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
- vim_hbo_1272 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