Application crash via invalid buffer pattern
Published May 8, 2022 · Updated Aug 3, 2024
NULL pointer dereference in Vim before 8.2.4901 allows attackers to crash the editor through a crafted invalid buffer pattern. When fname_match receives a pattern that fails to compile, it retries home-directory substitution even though rmp->regprog is NULL, and the retry dereferences that pointer. Triggering the flaw requires Vim to process the invalid pattern during buffer selection; the bounded consequence is an application crash.
Summary
What happened
NULL pointer dereference in Vim before 8.2.4901 allows attackers to crash the editor through a crafted invalid buffer pattern. When fname_match receives a pattern that fails to compile, it retries home-directory substitution even though rmp->regprog is NULL, and the retry dereferences that pointer. Triggering the flaw requires Vim to process the invalid pattern during buffer selection; the bounded consequence is an application crash.
The record
- CVE
- CVE-2022-1620
- Published
- May 8, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-476
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 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 <8.2.4901
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
- huntr.dev CVE-2022-1620 exploit artifactproof of concept · unverified
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