Process crash and memory corruption via stale pointer
Published Nov 19, 2021 · Updated Aug 3, 2024
Use-after-free in Vim before 8.2.3612 allows local users to crash the editor or corrupt memory through a mark-based NFA regular expression. In nfa_regmatch, getmark_buf can free the current line, but regexp_nfa.c continues through rex.line and rex.input without reacquiring that line. User interaction is required to run the crafted substitute expression; the stale pointer can terminate the Vim process or permit code execution in the user's context.
Summary
What happened
Use-after-free in Vim before 8.2.3612 allows local users to crash the editor or corrupt memory through a mark-based NFA regular expression. In nfa_regmatch, getmark_buf can free the current line, but regexp_nfa.c continues through rex.line and rex.input without reacquiring that line. User interaction is required to run the crafted substitute expression; the stale pointer can terminate the Vim process or permit code execution in the user's context.
The record
- CVE
- CVE-2021-3974
- Published
- Nov 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 19, 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.3612
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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_mark_position regression triggerproof 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