It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-761 advisory.

    Vim is an open source command line text editor. Vim < v9.1.0647 has double free in src/alloc.c:616. When     closing a window, the corresponding tagstack data will be cleared and freed. However a bit later, the     quickfix list belonging to that window will also be cleared and if that quickfix list points to the same     tagstack data, Vim will try to free it again, resulting in a double-free/use-after-free access exception.
    Impact is low since the user must intentionally execute vim with several non-default flags,but it may     cause a crash of Vim. The issue has been fixed as of Vim patch v9.1.0647 (CVE-2024-41957)

    The UNIX editor Vim prior to version 9.1.0678 has a use-after-free error in argument list handling. When     adding a new file to the argument list, this triggers `Buf*` autocommands. If in such an autocommand the     buffer that was just opened is closed (including the window where it is shown), this causes the window     structure to be freed which contains a reference to the argument list that we are actually modifying. Once     the autocommands are completed, the references to the window and argument list are no longer valid and as     such cause an use-after-free. Impact is low since the user must either intentionally add some unusual     autocommands that wipe a buffer during creation (either manually or by sourcing a malicious plugin), but     it will crash Vim. The issue has been fixed as of Vim patch v9.1.0678. (CVE-2024-43374)

    Vim is an improved version of the unix vi text editor. When flushing the typeahead buffer, Vim moves the     current position in the typeahead buffer but does not check whether there is enough space left in the     buffer to handle the next characters.  So this may lead to the tb_off position within the typebuf variable     to point outside of the valid buffer size, which can then later lead to a heap-buffer overflow in e.g.
    ins_typebuf(). Therefore, when flushing the typeahead buffer, check if there is enough space left before     advancing the off position. If not, fall back to flush current typebuf contents. It's not quite clear yet,     what can lead to this situation. It seems to happen when error messages occur (which will cause Vim to     flush the typeahead buffer) in comnination with several long mappgins and so it may eventually move the     off position out of a valid buffer size. Impact is low since it is not easily reproducible and requires to     have several mappings active and run into some error condition. But when this happens, this will cause a     crash. The issue has been fixed as of Vim patch v9.1.0697. Users are advised to upgrade. There are no     known workarounds for this issue. (CVE-2024-43802)

    Vim is an open source, command line text editor. A use-after-free was found in Vim < 9.1.0764. When     closing a buffer (visible in a window) a BufWinLeave auto command can cause an use-after-free if this auto     command happens to re-open the same buffer in a new split window. Impact is low since the user must have     intentionally set up such a strange auto command and run some buffer unload commands. However this may     lead to a crash. This issue has been addressed in version 9.1.0764 and all users are advised to upgrade.
    There are no known workarounds for this vulnerability. (CVE-2024-47814)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of vim installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-43802 advisory.

  - Vim is an improved version of the unix vi text editor. When flushing the typeahead buffer, Vim moves the     current position in the typeahead buffer but does not check whether there is enough space left in the     buffer to handle the next characters. So this May lead to the tb_off position within the typebuf variable     to point outside of the valid buffer size, which can then later lead to a heap-buffer overflow in e.g.
    ins_typebuf(). Therefore, when flushing the typeahead buffer, check if there is enough space left before     advancing the off position. If not, fall back to flush current typebuf contents. It's not quite clear yet,     what can lead to this situation. It seems to happen when error messages occur (which will cause Vim to     flush the typeahead buffer) in comnination with several long mappgins and so it May eventually move the     off position out of a valid buffer size. Impact is low since it is not easily reproducible and requires to     have several mappings active and run into some error condition. But when this happens, this will cause a     crash. The issue has been fixed as of Vim patch v9.1.0697. Users are advised to upgrade. There are no     known workarounds for this issue. (CVE-2024-43802)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-4097 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4097-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                         Sean Whitton     March 30, 2025                                https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : vim     Version        : 2:8.2.2434-3+deb11u3     CVE ID         : CVE-2021-3872 CVE-2021-4019 CVE-2021-4173 CVE-2021-4187                      CVE-2022-0261 CVE-2022-0351 CVE-2022-0359 CVE-2022-0361                      CVE-2022-0392 CVE-2022-0417 CVE-2022-0572 CVE-2022-1616                      CVE-2022-1785 CVE-2022-1897 CVE-2022-1942 CVE-2022-2000                      CVE-2022-2129 CVE-2022-2304 CVE-2022-3099 CVE-2022-3134                      CVE-2022-3324 CVE-2022-4141 CVE-2023-0054 CVE-2023-1175                      CVE-2023-2610 CVE-2023-4738 CVE-2023-4752 CVE-2023-4781                      CVE-2023-5344 CVE-2024-22667 CVE-2024-43802 CVE-2024-47814     Debian Bug     : 1015984 1019590 1027146 1031875 1035955 1053694 1084806

    Multiple vulnerabilities were discovered in vim, an enhanced vi editor.

    CVE-2021-3872

        Heap-based buffer overflow possible if the buffer name is very long.

    CVE-2021-4019

        Heap-based buffer overflow possible with a very long help argument.

    CVE-2021-4173

        Double free in the VimScript9 compiler with a nested :def function.

    CVE-2021-4187

        Double free in the VimScript9 compiler if a nested function has a         line break in its argument list.

    CVE-2022-0261

        Buffer overflow in block insert, which goes over the end of the line.

    CVE-2022-0351

        In a command, a condition with many parentheses can cause a crash,         because there was previously no recursion limit.

    CVE-2022-0359

        A heap-based buffer overflow could occur with a large tabstop in Ex         mode.

    CVE-2022-0361

        A buffer overflow was found in the code copying lines in Visual         mode.

    CVE-2022-0392

        A heap-based buffer overflow was found in the code handling         bracketed paste in ex mode.

    CVE-2022-0417

        The :retab 0 command may cause a buffer overflow because a limit         was set too high.

    CVE-2022-0572

        Repeatedly using the :retab command may have caused a crash.

    CVE-2022-1616

        There is a possbile buffer overflow when processing an invalid         command with composing characters.

    CVE-2022-1785

        It was possible to change the window in a substitute expression,         which could lead to an out-of-bounds write.

    CVE-2022-1897

        It was possible to use the undo command in a substitute expression,         leading to an invalid memory overwrite.

    CVE-2022-1942

        It was possible to open a command line window from a substitute         expression, leading to a heap-based buffer overflow.

    CVE-2022-2000

        Command error messages were not truncated, and as such could lead to         out-of-bounds writes.

    CVE-2022-2129

        It was possible to switch buffers in a substitute expression,         leading to a heap-based buffer overflow.

    CVE-2022-2304

        Long words might cause a buffer overflow in the spellchecker.

    CVE-2022-3099

        Line numbers in :for commands were not validated, which could lead         to a crash.

    CVE-2022-3134

        If a relevant window was unexpectedly closed while searching for         tags, vim would crash.

    CVE-2022-3324

        Negative window widths caused the use of a negative array index,         that is, an invalid read.

    CVE-2022-4141

        Functions that visit another file during a substitution could cause         a heap-based buffer overflow.

    CVE-2023-0054

        A recursive substitute expression could cause an out-of-bounds write.

    CVE-2023-1175

        When doing virtual editing, a buffer size calculation was wrong.

    CVE-2023-2610

        When expanding ~ in a substitution, if the resulting expansion was         very long, vim would crash.

    CVE-2023-4738

        A buffer overflow problem was found in vim_regsub_both().

    CVE-2023-4752

        A use-after-free problem was found in ins_compl_get_exp().

    CVE-2023-4781

        A second buffer overflow problem was found in vim_regsub_both().

    CVE-2023-5344

        trunc_string() made an incorrect assumption about when a certain         buffer would be writeable.

    CVE-2024-22667

        Several calls writing error messages did not check that there was         enough space for the full message.

    CVE-2024-43802

        The typeahead buffer end pointer could be moved past its end when         flushing that buffer, leading to an out-of-bounds read.

    CVE-2024-47814

        When splitting the window and editing a new buffer, the new buffer         could be marked for deletion, leading to a use-after-free.

    For Debian 11 bullseye, these problems have been fixed in version     2:8.2.2434-3+deb11u3.

    We recommend that you upgrade your vim packages.

    For the detailed security status of vim please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/vim

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

An update of the vim package has been released.

ID	Name	Product	Family	Published	Updated	Severity
211367	Amazon Linux 2023 : vim-common, vim-data, vim-default-editor (ALAS2023-2024-761)	Nessus	Amazon Linux Local Security Checks	11/14/2024	11/14/2024	medium
215553	Azure Linux 3.0 Security Update: vim (CVE-2024-43802)	Nessus	Azure Linux Local Security Checks	2/10/2025	9/15/2025	medium
233548	Debian dla-4097 : vim - security update	Nessus	Debian Local Security Checks	3/30/2025	3/30/2025	high
206944	Photon OS 5.0: Vim PHSA-2024-5.0-0371	Nessus	PhotonOS Local Security Checks	9/11/2024	10/11/2024	medium

Detections

Analytics

Plugins Search

medium

medium

high

medium