Unsafe memory access via stale assertion-error pointer
Published Aug 15, 2022 · Updated Aug 3, 2024
Use-after-free in Vim before 9.0.0213 allows local users to trigger unsafe memory access through a crafted assert_fails call. In f_assert_fails, pattern_match can free the v:errmsg buffer while the function still retains and later reads the same pointer. Exploitation requires user interaction to execute the affected assertion path; upstream documents the memory-lifetime error but not a demonstrated outcome beyond unsafe memory access.
Summary
What happened
Use-after-free in Vim before 9.0.0213 allows local users to trigger unsafe memory access through a crafted assert_fails call. In f_assert_fails, pattern_match can free the v:errmsg buffer while the function still retains and later reads the same pointer. Exploitation requires user interaction to execute the affected assertion path; upstream documents the memory-lifetime error but not a demonstrated outcome beyond unsafe memory access.
The record
- CVE
- CVE-2022-2817
- Published
- Aug 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 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.0213
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
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