One-byte memory disclosure via error pointer underflow
Published Jan 10, 2022 · Updated Aug 2, 2024
Out-of-bounds read in Vim before 8.2.4049 allows local users to disclose one byte of process memory through a crafted Vim9 script. When compile_get_env() parses a lone dollar sign, get_env_len() returns zero and the error path passes start minus one to semsg(), reading before the allocated line. Exploitation requires a victim to open the crafted file; the demonstrated consequence is limited to disclosure of one byte of Vim process memory.
Summary
What happened
Out-of-bounds read in Vim before 8.2.4049 allows local users to disclose one byte of process memory through a crafted Vim9 script. When compile_get_env() parses a lone dollar sign, get_env_len() returns zero and the error path passes start minus one to semsg(), reading before the allocated line. Exploitation requires a victim to open the crafted file; the demonstrated consequence is limited to disclosure of one byte of Vim process memory.
The record
- CVE
- CVE-2022-0158
- Published
- Jan 10, 2022
- Updated
- Aug 2, 2024
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-787, CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.
Weakness, pattern, technique
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