Process-memory disclosure via unchecked visual column
Published Dec 31, 2021 · Updated Aug 3, 2024
Out-of-bounds read in Vim before 8.2.3901 allows context-dependent attackers to disclose process memory through a crafted file. The getvcol() function calculates a pointer from an unchecked visual-column position that can lie beyond the line's terminating NUL byte. Opening the file and exercising the /%V visual-area atom is required; the read exposes adjacent Vim process memory without modifying data.
Summary
What happened
Out-of-bounds read in Vim before 8.2.3901 allows context-dependent attackers to disclose process memory through a crafted file. The getvcol() function calculates a pointer from an unchecked visual-column position that can lie beyond the line's terminating NUL byte. Opening the file and exercising the /%V visual-area atom is required; the read exposes adjacent Vim process memory without modifying data.
The record
- CVE
- CVE-2021-4193
- Published
- Dec 31, 2021
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 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.3901
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
- huntr.dev CVE-2021-4193 exploitproof of concept · unverified
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