Code execution via recursive substitute use-after-free
Published Jan 30, 2022 · Updated Aug 2, 2024
Use-after-free in Vim before 8.2.4253 allows local users to execute code or crash the editor by opening a crafted file. The ex_substitute function retains expression-substitution text that a recursive replacement function can free, then uses the stale allocation instead of preserving a copy. Exploitation requires a user to open attacker-controlled content that invokes the recursive substitution path; memory corruption remains within the Vim process but can execute code with that user's privileges.
Summary
What happened
Use-after-free in Vim before 8.2.4253 allows local users to execute code or crash the editor by opening a crafted file. The ex_substitute function retains expression-substitution text that a recursive replacement function can free, then uses the stale allocation instead of preserving a copy. Exploitation requires a user to open attacker-controlled content that invokes the recursive substitution path; memory corruption remains within the Vim process but can execute code with that user's privileges.
The record
- CVE
- CVE-2022-0413
- Published
- Jan 30, 2022
- Updated
- Aug 2, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 30, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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
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.
Public exploit references
- Test_using_old_sub regression reproducerproof 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