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.

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 remote Fedora 41 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-48e080c52f advisory.

    Security fix for CVE-2024-45306

    ----

    patchlevel 703

    Security fixes for CVE-2024-43374, CVE-2024-43802

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

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

According to the versions of the vim packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    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)

    Vim is an open source command line text editor. double-free in dialog_changed() in Vim  v9.1.0648. When     abandoning a buffer, Vim may ask the user what to do with the modified buffer. If the user wants the     changed buffer to be saved, Vim may create a new Untitled file, if the buffer did not have a name yet.
    However, when setting the buffer name to Unnamed, Vim will falsely free a pointer twice, leading to a     double-free and possibly later to a heap-use-after-free, which can lead to a crash. The issue has been     fixed as of Vim patch v9.1.0648.(CVE-2024-41965)

    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)

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

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

According to the versions of the vim packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    Vim is an open source command line text editor.double-free in dialog_changed() in Vim  v9.1.0648.When     abandoning a buffer, Vim may ask the user what to do with the modified buffer.If the user wants the     changed buffer to be saved, Vim may create a new Untitled file, if the buffer did not have a name     yet.However, when setting the buffer name to Unnamed, Vim will falsely free a pointer twice, leading to a     double-free and possibly later to a heap-use-after-free, which can lead to a crash.The issue has been     fixed as of Vim patch v9.1.0648.(CVE-2024-41965)

    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)

Tenable has extracted the preceding description block directly from the EulerOS vim 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 CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-43374 advisory.

  - 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)

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

The remote Fedora 39 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-055adf8e6f advisory.

    Security fix for CVE-2024-45306

    ----

    patchlevel 703

    Security fixes for CVE-2024-43374, CVE-2024-43802

Tenable has extracted the preceding description block directly from the Fedora 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 remote Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-6993-1 advisory.

    It was discovered that Vim incorrectly handled memory when closing a window, leading to a double-free     vulnerability. If a user was tricked into opening a specially crafted file, an attacker could crash the

    application, leading to a denial of service, or possibly achieve code

    execution with user privileges. (CVE-2024-41957)

    It was discovered that Vim incorrectly handled memory when adding a new file to an argument list, leading     to a use-after-free. If a user was

    tricked into opening a specially crafted file, an attacker could crash the application, leading to a     denial of service. (CVE-2024-43374)

Tenable has extracted the preceding description block directly from the Ubuntu 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 remote Fedora 40 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-bb4b6da0b6 advisory.

    patchlevel 703

    Security fixes for CVE-2024-43374, CVE-2024-43802

Tenable has extracted the preceding description block directly from the Fedora 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 host is prior to 9.1.0678. It is, therefore, affected by a vulnerability as referenced in the advisory.

  - 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)

Note that Nessus has not tested for this issue 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	Severity
211367	Amazon Linux 2023 : vim-common, vim-data, vim-default-editor (ALAS2023-2024-761)	Nessus	Amazon Linux Local Security Checks	medium
211032	Fedora 41 : vim (2024-48e080c52f)	Nessus	Fedora Local Security Checks	medium
210694	EulerOS 2.0 SP9 : vim (EulerOS-SA-2024-2841)	Nessus	Huawei Local Security Checks	medium
210682	EulerOS 2.0 SP10 : vim (EulerOS-SA-2024-2898)	Nessus	Huawei Local Security Checks	medium
210675	EulerOS 2.0 SP9 : vim (EulerOS-SA-2024-2823)	Nessus	Huawei Local Security Checks	medium
210651	EulerOS 2.0 SP10 : vim (EulerOS-SA-2024-2918)	Nessus	Huawei Local Security Checks	medium
207040	CBL Mariner 2.0 Security Update: vim (CVE-2024-43374)	Nessus	MarinerOS Local Security Checks	medium
207006	Fedora 39 : vim (2024-055adf8e6f)	Nessus	Fedora Local Security Checks	medium
206625	Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS : Vim vulnerabilities (USN-6993-1)	Nessus	Ubuntu Local Security Checks	medium
206414	Fedora 40 : vim (2024-bb4b6da0b6)	Nessus	Fedora Local Security Checks	medium
206156	Vim < 9.1.0678 Heap-Use	Nessus	Windows	medium
206091	Photon OS 5.0: Vim PHSA-2024-5.0-0352	Nessus	PhotonOS Local Security Checks	medium
206090	Photon OS 4.0: Vim PHSA-2024-4.0-0671	Nessus	PhotonOS Local Security Checks	medium

Detections

Analytics

CVE-2024-43374

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium