Memory corruption via invalid diff-block offset
Published Jun 27, 2022 · Updated Aug 3, 2024
Out-of-bounds write in Vim before 8.2.5164 allows local users to corrupt memory by inducing a victim to run a crafted script. diff_mark_adjust_tp retains a nonzero offset when every line in a diff block is deleted, leaving invalid diff-block values after buffer manipulation. The established consequence is invalid memory access; exploitation requires a victim to run an untrusted file in script mode.
Summary
What happened
Out-of-bounds write in Vim before 8.2.5164 allows local users to corrupt memory by inducing a victim to run a crafted script. diff_mark_adjust_tp retains a nonzero offset when every line in a diff block is deleted, leaving invalid diff-block values after buffer manipulation. The established consequence is invalid memory access; exploitation requires a victim to run an untrusted file in script mode.
The record
- CVE
- CVE-2022-2210
- Published
- Jun 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 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 <8.2
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
No public exploit references are available in this record.
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