7.8
CVSSv3

CVE-2022-4141

Published: 25/11/2022 Updated: 07/11/2023
CVSS v3 Base Score: 7.8 | Impact Score: 5.9 | Exploitability Score: 1.8
VMScore: 0

Vulnerability Summary

Heap based buffer overflow in vim/vim 9.0.0946 and below by allowing an malicious user to CTRL-W gf in the expression used in the RHS of the substitute command.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

vim vim

fedoraproject fedora 36

fedoraproject fedora 37

Vendor Advisories

Debian Bug report logs - #1027146 vim: CVE-2022-4141 Package: src:vim; Maintainer for src:vim is Debian Vim Maintainers <team+vim@trackerdebianorg>; Reported by: Moritz Mühlenhoff <jmm@inutilorg> Date: Wed, 28 Dec 2022 16:42:02 UTC Severity: important Tags: security, upstream Found in version vim/2:900813-1 Fi ...
The target's backtrace indicates that libc has detected a heap error or that the target was executing a heap function when it stopped This could be due to heap corruption, passing a bad pointer to a heap function such as free(), etc Since heap errors might include buffer overflows, use-after-free situations, etc they are generally considered exp ...
The target's backtrace indicates that libc has detected a heap error or that the target was executing a heap function when it stopped This could be due to heap corruption, passing a bad pointer to a heap function such as free(), etc Since heap errors might include buffer overflows, use-after-free situations, etc they are generally considered exp ...
DescriptionThe MITRE CVE dictionary describes this issue as: The target's backtrace indicates that libc has detected a heap error or that the target was executing a heap function when it stopped This could be due to heap corruption, passing a bad pointer to a heap function such as free(), etc Since heap errors might include buffer overflows, use- ...
The target's backtrace indicates that libc has detected a heap error or that the target was executing a heap function when it stopped This could be due to heap corruption, passing a bad pointer to a heap function such as free(), etc Since heap errors might include buffer overflows, use-after-free situations, etc they are generally considered exp ...