Memory corruption via empty-register put underflow
Published May 26, 2022 · Updated Aug 3, 2024
Heap buffer overflow in Vim before 8.2.5016 allows local users to corrupt memory by inducing a victim to execute a crafted put command. In do_put(), an empty register yields a zero length, yet the code subtracts one and passes the resulting pre-buffer pointer to mb_head_off(). Exploitation requires user interaction inside a local Vim session and can overwrite memory or crash the editor process.
Summary
What happened
Heap buffer overflow in Vim before 8.2.5016 allows local users to corrupt memory by inducing a victim to execute a crafted put command. In do_put(), an empty register yields a zero length, yet the code subtracts one and passes the resulting pre-buffer pointer to mb_head_off(). Exploitation requires user interaction inside a local Vim session and can overwrite memory or crash the editor process.
The record
- CVE
- CVE-2022-1886
- Published
- May 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, CWE-122
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 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?
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 empty-register put proof of conceptproof 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