Editor crash via unchecked assert_fails string conversion
Published Sep 8, 2022 · Updated Aug 3, 2024
NULL pointer dereference in Vim before 9.0.0404 allows local users to crash the editor by supplying invalid assert_fails() arguments. In src/testing.c, f_assert_fails() passes an unchecked NULL result from tv_get_string_buf_chk() to pattern_match() when a list element is not a string. Exploitation requires execution of Vim script containing the invalid argument, and the bounded consequence is termination of that Vim process.
Summary
What happened
NULL pointer dereference in Vim before 9.0.0404 allows local users to crash the editor by supplying invalid assert_fails() arguments. In src/testing.c, f_assert_fails() passes an unchecked NULL result from tv_get_string_buf_chk() to pattern_match() when a list element is not a string. Exploitation requires execution of Vim script containing the invalid argument, and the bounded consequence is termination of that Vim process.
The record
- CVE
- CVE-2022-3153
- Published
- Sep 8, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.0404
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
- assert_fails() invalid-argument regression caseproof 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