CVE-2022-0714 Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436.

CVE-2022-0714 Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436.

This is a heap-based buffer overflow in Vim’s tag-listing functionality. When a user is editing a repository on GitHub and presses the :Tag command, Vim will parse the commit message, construct a tree of changes, and display the commit message and list of files on the screen. This is pretty boring stuff, but it can be exploited to cause a heap-based buffer overflow. The tag-listing functionality can be invoked by specifying a file: line number, e.g.: :!vim /path/to/repo.git The parsing of the commit message results in some dynamic security checks. As long as the user has write access to a GitHub repository and has the right permissions, this will cause the tag-listing functionality to be invoked. In order to exploit this issue, an attacker needs to have write access to the repository. This can be achieved by tricking the user into granting write access to the attacker’s account. This can be done via phishing, social engineering, or through the use of a malicious extension.

CVE-2022-0715

This vulnerability is a vulnerability in the Vim text editing program. It will not allow users to enter commands for a specific file or path without entering the correct command. The vulnerability exists because the software does not verify that the input matches what it expects from a user before executing it. This allows an attacker to create malicious files by creating a file and linking it to an existing file. The exploit occurs when an attacker creates a new file, names it with one of these patterns:

VIM Plugin

- %H
This is a buffer overflow in Vim’s tag-listing functionality. The tag-listing functionality can be invoked by specifying a file: line number, e.g.: :!vim /path/to/repo.git The parsing of the commit message results in some dynamic security checks. As long as the user has write access to a GitHub repository and has the right permissions, this will cause the tag-listing functionality to be invoked. In order to exploit this issue, an attacker needs to have write access to the repository. This can be achieved by tricking the user into granting write access to the attacker’s account. This can be done via phishing, social engineering, or through the use of a malicious extension.

References

Subscribe to CVE.news
Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe