Memory corruption via unchecked substitution result length
Published Sep 2, 2023 · Updated Nov 3, 2025
Heap-based buffer overflow in Vim before 9.0.1848 allows local users to corrupt memory by processing a crafted Vim script. The vim_regsub_both function copies an evaluated substitution result into a destination buffer without confirming that it fits the remaining capacity. A user must open or source crafted content, and the upstream regression test demonstrates a Vim process crash.
Summary
What happened
Heap-based buffer overflow in Vim before 9.0.1848 allows local users to corrupt memory by processing a crafted Vim script. The vim_regsub_both function copies an evaluated substitution result into a destination buffer without confirming that it fits the remaining capacity. A user must open or source crafted content, and the upstream regression test demonstrates a Vim process crash.
The record
- CVE
- CVE-2023-4738
- Published
- Sep 2, 2023
- Updated
- Nov 3, 2025
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2023CVE 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.1848
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
- Upstream vim_regsub_both crash regression inputproof 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