Memory corruption via tagfunc-triggered buffer deletion
Published Aug 23, 2022 · Updated Aug 3, 2024
Use-after-free in Vim before 9.0.0246 allows local users to corrupt process memory by invoking a tag function that deletes its buffer. In do_tag() in src/tag.c, Vim retains a pointer to a tag-stack name while the configured tagfunc callback can wipe the buffer and free that storage. Triggering the flaw requires user interaction with a configured tag function; the stale-pointer access can crash Vim or corrupt its process memory.
Summary
What happened
Use-after-free in Vim before 9.0.0246 allows local users to corrupt process memory by invoking a tag function that deletes its buffer. In do_tag() in src/tag.c, Vim retains a pointer to a tag-stack name while the configured tagfunc callback can wipe the buffer and free that storage. Triggering the flaw requires user interaction with a configured tag function; the stale-pointer access can crash Vim or corrupt its process memory.
The record
- CVE
- CVE-2022-2946
- Published
- Aug 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 23, 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.0246
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 CVE-2022-2946 proof of conceptproof 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