Memory corruption via stale open-command line pointer
Published Dec 6, 2021 · Updated Aug 3, 2024
Use-after-free in Vim before 8.2.3741 allows local users to corrupt memory or crash the editor through a crafted :open pattern. The ex_open function retains a pointer to the current line while mark lookup can flush that line, then uses the stale pointer for matching. Triggering requires execution of the crafted Ex command; the demonstrated regression case accesses freed memory, while broader code execution is not established.
Summary
What happened
Use-after-free in Vim before 8.2.3741 allows local users to corrupt memory or crash the editor through a crafted :open pattern. The ex_open function retains a pointer to the current line while mark lookup can flush that line, then uses the stale pointer for matching. Triggering requires execution of the crafted Ex command; the demonstrated regression case accesses freed memory, while broader code execution is not established.
The record
- CVE
- CVE-2021-4069
- Published
- Dec 6, 2021
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2021CVE 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
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
- Upstream :open use-after-free 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