Local crash via premature log error handling
Published Feb 12, 2025 · Updated Mar 21, 2025
Memory corruption in Vim 9.1.1096 and earlier allows local users to crash the editor by supplying an inaccessible path to --log. During early argument scanning, Vim logs the file-open error before estack_init() has initialized the execution stack, causing an invalid memory read. The user must execute a build containing +channel with an inaccessible log path; the demonstrated consequence is process termination.
Summary
What happened
Memory corruption in Vim 9.1.1096 and earlier allows local users to crash the editor by supplying an inaccessible path to --log. During early argument scanning, Vim logs the file-open error before estack_init() has initialized the execution stack, causing an invalid memory read. The user must execute a build containing +channel with an inaccessible log path; the demonstrated consequence is process termination.
The record
- CVE
- CVE-2025-1215
- Published
- Feb 12, 2025
- Updated
- Mar 21, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-119, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- Mar 21, 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=9.1.1096
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 inaccessible --log path 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