Editor crash via unchecked comment-leader offset
Published Jan 21, 2023 · Updated Apr 2, 2025
Heap buffer overflow in Vim before 9.0.1225 allows context-dependent attackers to crash the editor via a crafted text line. The same_leader() routine in src/textformat.c adds a comment-leader length to a line pointer without verifying that the line is that long, causing an out-of-bounds heap read. A user must load attacker-controlled text and invoke text formatting; SUSE assesses the consequence as an application crash without confidentiality or integrity impact.
Summary
What happened
Heap buffer overflow in Vim before 9.0.1225 allows context-dependent attackers to crash the editor via a crafted text line. The same_leader() routine in src/textformat.c adds a comment-leader length to a line pointer without verifying that the line is that long, causing an out-of-bounds heap read. A user must load attacker-controlled text and invoke text formatting; SUSE assesses the consequence as an application crash without confidentiality or integrity impact.
The record
- CVE
- CVE-2023-0433
- Published
- Jan 21, 2023
- Updated
- Apr 2, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2023CVE publishedPublication date reported by the CVE source.
- Apr 2, 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.1225
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.
Public exploit references
No public exploit references are available in this record.
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