It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS-2022-1557 advisory.

    2024-05-09: CVE-2020-20703 was added to this advisory.

    Buffer Overflow vulnerability in VIM v.8.1.2135 allows a remote attacker to execute arbitrary code via the     operand parameter. (CVE-2020-20703)

    vim is vulnerable to Heap-based Buffer Overflow (CVE-2021-3903)

    A flaw was found in vim. A possible heap-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. The highest threat from this vulnerability is     to data confidentiality and integrity as well as system availability. (CVE-2021-3927)

    A flaw was found in vim. A possible stack-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. The highest threat from this vulnerability is     to data confidentiality and integrity as well as system availability. (CVE-2021-3928)

    A flaw was found in vim. A possible heap use-after-free vulnerability could allow an attacker to input a     specially crafted file leading to a crash or code execution. The highest threat from this vulnerability is     to system availability. (CVE-2021-3968)

    A flaw was found in vim. A possible heap-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. The highest threat from this vulnerability is     to system availability. (CVE-2021-3973)

    A flaw was found in vim. A possible use-after-free vulnerability could allow an attacker to input a     specially crafted file leading to a crash or code execution. The highest threat from this vulnerability is     to system availability. (CVE-2021-3974)

    A flaw was found in vim. A possible heap-based buffer overflow allows an attacker to input a specially     crafted file, leading to a crash or code execution. The highest threat from this vulnerability is     confidentiality, integrity, and system availability. (CVE-2021-3984)

    A flaw was found in vim. A possible heap-based buffer overflow vulnerability allows an attacker to input a     specially crafted file, leading to a crash or code execution. The highest threat from this vulnerability     is system availability. (CVE-2021-4019)

    vim is vulnerable to Use After Free (CVE-2021-4069)

    A flaw was found in vim. A possible heap-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. (CVE-2021-4136)

    A flaw was found in vim. A possible heap-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. (CVE-2021-4166)

    A flaw was found in vim. A possible use after free vulnerability could allow an attacker to input a     specially crafted file leading to a crash or code execution. (CVE-2021-4173)

    A flaw was found in vim. A possible use after free vulnerability could allow an attacker to input a     specially crafted file leading to a crash or code execution. (CVE-2021-4187)

    It was found that vim was vulnerable to use-after-free flaw in win_linetabsize(). Sourcing a specially     crafted file in vim could crash the vim process or possibly lead to other undefined behaviors.
    (CVE-2021-4192)

    It was found that vim was vulnerable to an out-of-bound read flaw in getvcol(). A specially crafted file     could be used to, when opened in vim, disclose some of the process's internal memory. (CVE-2021-4193)

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 SUSE Linux SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:4619-1 advisory.

    Updated to version 9.0.0814:

      * Fixing bsc#1192478 VUL-1: CVE-2021-3928: vim: vim is vulnerable to Stack-based Buffer Overflow
      * Fixing bsc#1203508 VUL-0: CVE-2022-3234: vim: Heap-based Buffer Overflow prior to 9.0.0483.
      * Fixing bsc#1203509 VUL-1: CVE-2022-3235: vim: Use After Free in GitHub prior to 9.0.0490.
      * Fixing bsc#1203820 VUL-0: CVE-2022-3324: vim: Stack-based Buffer Overflow in prior to 9.0.0598.
      * Fixing bsc#1204779 VUL-0: CVE-2022-3705: vim: use after free in function qf_update_buffer of the file     quickfix.c
      * Fixing bsc#1203152 VUL-1: CVE-2022-2982: vim: use after free in qf_fill_buffer()
      * Fixing bsc#1203796 VUL-1: CVE-2022-3296: vim: stack out of bounds read in ex_finally() in ex_eval.c
      * Fixing bsc#1203797 VUL-1: CVE-2022-3297: vim: use-after-free in process_next_cpt_value() at     insexpand.c
      * Fixing bsc#1203110 VUL-1: CVE-2022-3099: vim: Use After Free in ex_docmd.c
      * Fixing bsc#1203194 VUL-1: CVE-2022-3134: vim: use after free in do_tag()
      * Fixing bsc#1203272 VUL-1: CVE-2022-3153: vim: NULL Pointer Dereference in GitHub repository vim/vim     prior to 9.0.0404.
      * Fixing bsc#1203799 VUL-1: CVE-2022-3278: vim: NULL pointer dereference in eval_next_non_blank() in     eval.c
      * Fixing bsc#1203924 VUL-1: CVE-2022-3352: vim: vim: use after free
      * Fixing bsc#1203155 VUL-1: CVE-2022-2980: vim: null pointer dereference in do_mouse()
      * Fixing bsc#1202962 VUL-1: CVE-2022-3037: vim: Use After Free in vim prior to 9.0.0321
      * Fixing bsc#1200884 Vim: Error on startup
      * Fixing bsc#1200902 VUL-0: CVE-2022-2183: vim: Out-of-bounds Read through get_lisp_indent() Mon 13:32
      * Fixing bsc#1200903 VUL-0: CVE-2022-2182: vim: Heap-based Buffer Overflow through parse_cmd_address()     Tue 08:37
      * Fixing bsc#1200904 VUL-0: CVE-2022-2175: vim: Buffer Over-read through cmdline_insert_reg() Tue 08:37
      * Fixing bsc#1201249 VUL-0: CVE-2022-2304: vim: stack buffer overflow in spell_dump_compl()
      * Fixing bsc#1201356 VUL-1: CVE-2022-2343: vim: Heap-based Buffer Overflow in GitHub repository vim     prior to 9.0.0044
      * Fixing bsc#1201359 VUL-1: CVE-2022-2344: vim: Another Heap-based Buffer Overflow vim prior to 9.0.0045
      * Fixing bsc#1201363 VUL-1: CVE-2022-2345: vim: Use After Free in GitHub repository vim prior to     9.0.0046.
      * Fixing bsc#1201620 vim: SLE-15-SP4-Full-x86_64-GM-Media1 and vim-plugin-tlib-1.27-bp154.2.18.noarch     issue
      * Fixing bsc#1202414 VUL-1: CVE-2022-2819: vim: Heap-based Buffer Overflow in compile_lock_unlock()
      * Fixing bsc#1202552 VUL-1: CVE-2022-2874: vim: NULL Pointer Dereference in generate_loadvar()
      * Fixing bsc#1200270 VUL-1: CVE-2022-1968: vim: use after free in utf_ptr2char
      * Fixing bsc#1200697 VUL-1: CVE-2022-2124: vim: out of bounds read in current_quote()
      * Fixing bsc#1200698 VUL-1: CVE-2022-2125: vim: out of bounds read in get_lisp_indent()
      * Fixing bsc#1200700 VUL-1: CVE-2022-2126: vim: out of bounds read in suggest_trie_walk()
      * Fixing bsc#1200701 VUL-1: CVE-2022-2129: vim: out of bounds write in vim_regsub_both()
      * Fixing bsc#1200732 VUL-1: CVE-2022-1720: vim: out of bounds read in grab_file_name()
      * Fixing bsc#1201132 VUL-1: CVE-2022-2264: vim: out of bounds read in inc()
      * Fixing bsc#1201133 VUL-1: CVE-2022-2284: vim: out of bounds read in utfc_ptr2len()
      * Fixing bsc#1201134 VUL-1: CVE-2022-2285: vim: negative size passed to memmove() due to integer     overflow
      * Fixing bsc#1201135 VUL-1: CVE-2022-2286: vim: out of bounds read in ins_bytes()
      * Fixing bsc#1201136 VUL-1: CVE-2022-2287: vim: out of bounds read in suggest_trie_walk()
      * Fixing bsc#1201150 VUL-1: CVE-2022-2231: vim: null pointer dereference skipwhite()
      * Fixing bsc#1201151 VUL-1: CVE-2022-2210: vim: out of bounds read in ml_append_int()
      * Fixing bsc#1201152 VUL-1: CVE-2022-2208: vim: null pointer dereference in diff_check()
      * Fixing bsc#1201153 VUL-1: CVE-2022-2207: vim: out of bounds read in ins_bs()
      * Fixing bsc#1201154 VUL-1: CVE-2022-2257: vim: out of bounds read in msg_outtrans_special()
      * Fixing bsc#1201155 VUL-1: CVE-2022-2206: vim: out of bounds read in msg_outtrans_attr()
      * Fixing bsc#1201863 VUL-1: CVE-2022-2522: vim: out of bounds read via nested autocommand
      * Fixing bsc#1202046 VUL-1: CVE-2022-2571: vim: Heap-based Buffer Overflow related to     ins_comp_get_next_word_or_line()
      * Fixing bsc#1202049 VUL-1: CVE-2022-2580: vim: Heap-based Buffer Overflow related to eval_string()
      * Fixing bsc#1202050 VUL-1: CVE-2022-2581: vim: Out-of-bounds Read related to cstrchr()
      * Fixing bsc#1202051 VUL-1: CVE-2022-2598: vim: Undefined Behavior for Input to API related to     diff_mark_adjust_tp() and ex_diffgetput()
      * Fixing bsc#1202420 VUL-1: CVE-2022-2817: vim: Use After Free in f_assert_fails()
      * Fixing bsc#1202421 VUL-1: CVE-2022-2816: vim: Out-of-bounds Read in check_vim9_unlet()
      * Fixing bsc#1202511 VUL-1: CVE-2022-2862: vim: use-after-free in compile_nested_function()
      * Fixing bsc#1202512 VUL-1: CVE-2022-2849: vim: Invalid memory access related to mb_ptr2len()
      * Fixing bsc#1202515 VUL-1: CVE-2022-2845: vim: Buffer Over-read related to display_dollar()
      * Fixing bsc#1202599 VUL-1: CVE-2022-2889: vim: use-after-free in find_var_also_in_script() in     evalvars.c
      * Fixing bsc#1202687 VUL-1: CVE-2022-2923: vim: NULL Pointer Dereference in GitHub repository vim/vim     prior to 9.0.0240
      * Fixing bsc#1202689 VUL-1: CVE-2022-2946: vim: use after free in function vim_vsnprintf_typval
      * Fixing bsc#1202862 VUL-1: CVE-2022-3016: vim: Use After Free in vim prior to 9.0.0285 Mon 12:00
      * Fixing bsc#1191770 VUL-0: CVE-2021-3875: vim: heap-based buffer overflow
      * Fixing bsc#1192167 VUL-0: CVE-2021-3903: vim: heap-based buffer overflow
      * Fixing bsc#1192902 VUL-0: CVE-2021-3968: vim: vim is vulnerable to         Heap-based Buffer Overflow
      * Fixing bsc#1192903 VUL-0: CVE-2021-3973: vim: vim is vulnerable to         Heap-based Buffer Overflow
      * Fixing bsc#1192904 VUL-0: CVE-2021-3974: vim: vim is vulnerable to Use         After Free
      * Fixing bsc#1193466 VUL-1: CVE-2021-4069: vim: use-after-free in ex_open()         in src/ex_docmd.c
      * Fixing bsc#1193905 VUL-0: CVE-2021-4136: vim: vim is vulnerable to         Heap-based Buffer Overflow
      * Fixing bsc#1194093 VUL-1: CVE-2021-4166: vim: vim is vulnerable to         Out-of-bounds Read
      * Fixing bsc#1194216 VUL-1: CVE-2021-4193: vim: vulnerable to         Out-of-bounds Read
      * Fixing bsc#1194217 VUL-0: CVE-2021-4192: vim: vulnerable to Use After Free
      * Fixing bsc#1194872 VUL-0: CVE-2022-0261: vim: Heap-based Buffer Overflow         in vim prior to 8.2.
      * Fixing bsc#1194885 VUL-0: CVE-2022-0213: vim: vim is vulnerable to         Heap-based Buffer Overflow
      * Fixing bsc#1195004 VUL-0: CVE-2022-0318: vim: Heap-based Buffer Overflow in         vim prior to 8.2.
      * Fixing bsc#1195203 VUL-0: CVE-2022-0359: vim: heap-based buffer overflow in         init_ccline() in ex_getln.c
      * Fixing bsc#1195354 VUL-0: CVE-2022-0407: vim: Heap-based Buffer Overflow in         Conda vim prior to 8.2.
      * Fixing bsc#1198596 VUL-0: CVE-2022-1381: vim: global heap buffer overflow         in skip_range
      * Fixing bsc#1199331 VUL-0: CVE-2022-1616: vim: Use after free in         append_command
      * Fixing bsc#1199333 VUL-0: CVE-2022-1619: vim: Heap-based Buffer Overflow in         function cmdline_erase_chars
      * Fixing bsc#1199334 VUL-0: CVE-2022-1620: vim: NULL Pointer Dereference in         function vim_regexec_string
      * Fixing bsc#1199747 VUL-0: CVE-2022-1796: vim: Use After in         find_pattern_in_path
      * Fixing bsc#1200010 VUL-0: CVE-2022-1897: vim: Out-of-bounds Write in vim
      * Fixing bsc#1200011 VUL-0: CVE-2022-1898: vim: Use After Free in vim prior         to 8.2
      * Fixing bsc#1200012 VUL-0: CVE-2022-1927: vim: Buffer Over-read in vim prior         to 8.2
      * Fixing bsc#1070955 VUL-1: CVE-2017-17087: vim: Sets the group ownership of a         .swp file to the editor's primary group, which allows local users to obtain         sensitive information
      * Fixing bsc#1194388 VUL-1: CVE-2022-0128: vim: vim is vulnerable to         Out-of-bounds Read
      * Fixing bsc#1195332 VUL-1: CVE-2022-0392: vim: Heap-based Buffer Overflow         in vim prior to 8.2
      * Fixing bsc#1196361 VUL-1: CVE-2022-0696: vim: NULL Pointer Dereference in         vim prior to 8.2
      * Fixing bsc#1198748 VUL-1: CVE-2022-1420: vim: Out-of-range Pointer Offset
      * Fixing bsc#1199651 VUL-1: CVE-2022-1735: vim: heap buffer overflow
      * Fixing bsc#1199655 VUL-1: CVE-2022-1733: vim: Heap-based Buffer Overflow in         cindent.c
      * Fixing bsc#1199693 VUL-1: CVE-2022-1771: vim: stack exhaustion in vim prior         to 8.2.
      * Fixing bsc#1199745 VUL-1: CVE-2022-1785: vim: Out-of-bounds Write
      * Fixing bsc#1199936 VUL-1: CVE-2022-1851: vim: out of bounds read
      * Fixing bsc#1195004 - (CVE-2022-0318) VUL-0: CVE-2022-0318: vim: Heap-based Buffer Overflow in vim     prior to 8.2.
      * Fixing bsc#1190570 CVE-2021-3796: vim: use-after-free in nv_replace() in normal.c
      * Fixing bsc#1191893 CVE-2021-3872: vim: heap-based buffer overflow in win_redr_status() drawscreen.c
      * Fixing bsc#1192481 CVE-2021-3927: vim: vim is vulnerable to Heap-based Buffer Overflow
      * Fixing bsc#1192478 CVE-2021-3928: vim: vim is vulnerable to Stack-based Buffer Overflow
      * Fixing bsc#1193294 CVE-2021-4019: vim: vim is vulnerable to Heap-based Buffer Overflow
      * Fixing bsc#1193298 CVE-2021-3984: vim: illegal memory access when C-indenting could lead to Heap     Buffer Overflow
      * Fixing bsc#1190533 CVE-2021-3778: vim: Heap-based Buffer Overflow in regexp_nfa.c
      *  Fixing bsc#1194216 CVE-2021-4193: vim: vulnerable to Out-of-bounds Read
      * Fixing bsc#1194556 CVE-2021-46059: vim: A Pointer Dereference vulnerability         exists in Vim 8.2.3883 via the vim_regexec_multi function at regexp.c, which causes a denial of     service.
      * Fixing bsc#1195066 CVE-2022-0319: vim: Out-of-bounds Read in vim/vim prior to 8.2.
      * Fixing bsc#1195126 CVE-2022-0351: vim: uncontrolled recursion in eval7()
      * Fixing bsc#1195202 CVE-2022-0361: vim: Heap-based Buffer Overflow in vim prior to 8.2.
      * Fixing bsc#1195356 CVE-2022-0413: vim: use after free in src/ex_cmds.c

Tenable has extracted the preceding description block directly from the SUSE 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 host is running a version of macOS / Mac OS X that is 12.x prior to 12.3 Monterey. It is, therefore, affected by multiple vulnerabilities, including the following:
  - A use after free issue was addressed with improved memory management. Successful exploitation could   result in arbitrary code execution with kernel privileges (CVE-2022-22614). 

  - A logic issue was addressed with improved state management. Successful exploitation could result in   privilege escalation (CVE-2022-22632).

  - A null pointer dereference was addressed with improved validation. Successful exploitation could   result in a denial of service condition. (CVE-2022-22638).

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

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

  - vim is vulnerable to Out-of-bounds Read (CVE-2021-4166, CVE-2021-4193)

  - vim is vulnerable to Use After Free (CVE-2021-4192)

  - vim is vulnerable to Heap-based Buffer Overflow (CVE-2022-0213)

  - Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. (CVE-2022-0261, CVE-2022-0359,     CVE-2022-0361, CVE-2022-0572)

  - Heap-based Buffer Overflow in vim/vim prior to 8.2. (CVE-2022-0318)

  - Out-of-bounds Read in vim/vim prior to 8.2. (CVE-2022-0319)

  - Access of Memory Location Before Start of Buffer in GitHub repository vim/vim prior to 8.2.
    (CVE-2022-0351)

  - Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. (CVE-2022-0368)

  - Heap-based Buffer Overflow in GitHub repository vim prior to 8.2. (CVE-2022-0392)

  - Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. (CVE-2022-0408, CVE-2022-0629)

  - Use After Free in GitHub repository vim/vim prior to 8.2. (CVE-2022-0413, CVE-2022-0443)

  - Heap-based Buffer Overflow GitHub repository vim/vim prior to 8.2. (CVE-2022-0417)

  - Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2. (CVE-2022-0554)

  - Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4418. (CVE-2022-0685)

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

  - Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4440. (CVE-2022-0729)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

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

  - vim is vulnerable to Out-of-bounds Read (CVE-2021-4166, CVE-2021-4193)

  - vim is vulnerable to Use After Free (CVE-2021-4192)

  - vim is vulnerable to Heap-based Buffer Overflow (CVE-2022-0213)

  - Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. (CVE-2022-0261, CVE-2022-0359,     CVE-2022-0361)

  - Heap-based Buffer Overflow in vim/vim prior to 8.2. (CVE-2022-0318)

  - Access of Memory Location Before Start of Buffer in GitHub repository vim/vim prior to 8.2.
    (CVE-2022-0351)

  - Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. (CVE-2022-0368)

  - Heap-based Buffer Overflow in GitHub repository vim prior to 8.2. (CVE-2022-0392)

  - Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. (CVE-2022-0408)

  - Use After Free in GitHub repository vim/vim prior to 8.2. (CVE-2022-0413, CVE-2022-0443)

  - Heap-based Buffer Overflow GitHub repository vim/vim prior to 8.2. (CVE-2022-0417)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

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

  - vim is vulnerable to Out-of-bounds Read (CVE-2021-4166, CVE-2021-4193)

  - vim is vulnerable to Use After Free (CVE-2021-4192)

  - vim is vulnerable to Heap-based Buffer Overflow (CVE-2022-0213)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

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

  - vim is vulnerable to Out-of-bounds Read (CVE-2021-4166, CVE-2021-4193)

  - vim is vulnerable to Use After Free (CVE-2021-4192)

  - vim is vulnerable to Heap-based Buffer Overflow (CVE-2022-0213)

  - Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. (CVE-2022-0261, CVE-2022-0359,     CVE-2022-0361)

  - Heap-based Buffer Overflow in vim/vim prior to 8.2. (CVE-2022-0318)

  - Access of Memory Location Before Start of Buffer in GitHub repository vim/vim prior to 8.2.
    (CVE-2022-0351)

  - Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. (CVE-2022-0368)

  - Heap-based Buffer Overflow in GitHub repository vim prior to 8.2. (CVE-2022-0392)

  - Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. (CVE-2022-0408)

  - Use After Free in GitHub repository vim/vim prior to 8.2. (CVE-2022-0413, CVE-2022-0443)

  - Heap-based Buffer Overflow GitHub repository vim/vim prior to 8.2. (CVE-2022-0417)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

An update of the vim package has been released.

The remote host is running a version of macOS / Mac OS X that is 11.x prior to 11.6.6. It is, therefore, affected by multiple vulnerabilities:

  - zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many     distant matches. (CVE-2018-25032)

  - A logic issue was addressed with improved restrictions. This issue is fixed in macOS Monterey 12.1,     watchOS 8.3, iOS 15.2 and iPadOS 15.2, macOS Big Sur 11.6.2. A malicious application may be able to bypass     certain Privacy preferences. (CVE-2021-30946)

  - vim is vulnerable to Heap-based Buffer Overflow (CVE-2021-4136)

  - vim is vulnerable to Out-of-bounds Read (CVE-2021-4166, CVE-2021-4193, CVE-2022-0128)

  - vim is vulnerable to Use After Free (CVE-2021-4173, CVE-2021-4187, CVE-2021-4192)

  - A crafted URI sent to httpd configured as a forward proxy (ProxyRequests on) can cause a crash (NULL     pointer dereference) or, for configurations mixing forward and reverse proxy declarations, can allow for     requests to be directed to a declared Unix Domain Socket endpoint (Server Side Request Forgery). This     issue affects Apache HTTP Server 2.4.7 up to 2.4.51 (included). (CVE-2021-44224)

  - A carefully crafted request body can cause a buffer overflow in the mod_lua multipart parser     (r:parsebody() called from Lua scripts). The Apache httpd team is not aware of an exploit for the     vulnerabilty though it might be possible to craft one. This issue affects Apache HTTP Server 2.4.51 and     earlier. (CVE-2021-44790)

  - In zsh before 5.8.1, an attacker can achieve code execution if they control a command output inside the     prompt, as demonstrated by a %F argument. This occurs because of recursive PROMPT_SUBST expansion.
    (CVE-2021-45444)

  - Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn     by its CNA. Further investigation showed that it was not a security issue. Notes: none (CVE-2021-46059)

  - A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local     string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially     crafted zip file, leading to a crash or code execution. (CVE-2022-0530)

  - The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop     forever for non-prime moduli. Internally this function is used when parsing certificates that contain     elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point     encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has     invalid explicit curve parameters. Since certificate parsing happens prior to verification of the     certificate signature, any process that parses an externally supplied certificate may thus be subject to a     denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they     can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients     consuming server certificates - TLS servers consuming client certificates - Hosting providers taking     certificates or private keys from customers - Certificate authorities parsing certification requests from     subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that     use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS     issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate     which makes it slightly harder to trigger the infinite loop. However any operation which requires the     public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-     signed certificate to trigger the loop during verification of the certificate signature. This issue     affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the     15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected     1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc). (CVE-2022-0778)

  - A validation issue was addressed with improved input sanitization. This issue is fixed in iOS 15.3 and     iPadOS 15.3, watchOS 8.4, tvOS 15.3, Safari 15.3, macOS Monterey 12.2. Processing a maliciously crafted     mail message may lead to running arbitrary javascript. (CVE-2022-22589)

  - A use after free issue was addressed with improved memory management. This issue is fixed in macOS Big Sur     11.6.6, macOS Monterey 12.3, Security Update 2022-004 Catalina. A remote user may cause an unexpected app     termination or arbitrary code execution (CVE-2022-22630)

  - This issue was addressed with improved checks to prevent unauthorized actions. This issue is fixed in iOS     15.4 and iPadOS 15.4, Security Update 2022-004 Catalina, macOS Monterey 12.3, macOS Big Sur 11.6.6. A     malicious application may bypass Gatekeeper checks. (CVE-2022-22663)

  - A logic issue was addressed with improved validation. This issue is fixed in macOS Monterey 12.3. A     malicious application may be able to gain root privileges. (CVE-2022-22665)

  - An out-of-bounds read issue existed that led to the disclosure of kernel memory. This was addressed with     improved input validation. This issue is fixed in macOS Monterey 12.3.1, Security Update 2022-004     Catalina, macOS Big Sur 11.6.6. A local user may be able to read kernel memory. (CVE-2022-22674)

  - An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS     15.5, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey 12.3.1, iOS 15.4.1 and iPadOS 15.4.1. An     application may be able to execute arbitrary code with kernel privileges. Apple is aware of a report that     this issue may have been actively exploited.. (CVE-2022-22675)

  - A carefully crafted request body can cause a read to a random memory area which could cause the process to     crash. This issue affects Apache HTTP Server 2.4.52 and earlier. (CVE-2022-22719)

  - Apache HTTP Server 2.4.52 and earlier fails to close inbound connection when errors are encountered     discarding the request body, exposing the server to HTTP Request Smuggling (CVE-2022-22720)

  - If LimitXMLRequestBody is set to allow request bodies larger than 350MB (defaults to 1M) on 32 bit systems     an integer overflow happens which later causes out of bounds writes. This issue affects Apache HTTP Server     2.4.52 and earlier. (CVE-2022-22721)

  - valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes. (CVE-2022-23308)

  - An out-of-bounds read issue was addressed with improved input validation. This issue is fixed in Security     Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. Processing a maliciously crafted     AppleScript binary may result in unexpected application termination or disclosure of process memory.
    (CVE-2022-26697)

  - An out-of-bounds read issue was addressed with improved bounds checking. This issue is fixed in Security     Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. Processing a maliciously crafted     AppleScript binary may result in unexpected application termination or disclosure of process memory.
    (CVE-2022-26698)

  - An access issue was addressed with additional sandbox restrictions on third-party applications. This issue     is fixed in tvOS 15.5, iOS 15.5 and iPadOS 15.5, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey 12.4. A     sandboxed process may be able to circumvent sandbox restrictions. (CVE-2022-26706)

  - This issue was addressed by removing the vulnerable code. This issue is fixed in macOS Monterey 12.4,     macOS Big Sur 11.6.6. A malicious application may be able to modify protected parts of the file system.
    (CVE-2022-26712)

  - A memory corruption issue was addressed with improved validation. This issue is fixed in tvOS 15.5, iOS     15.5 and iPadOS 15.5, Security Update 2022-004 Catalina, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey     12.4. An application may be able to execute arbitrary code with kernel privileges. (CVE-2022-26714)

  - An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in Security     Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. An application may be able to gain     elevated privileges. (CVE-2022-26715)

  - An out-of-bounds read issue was addressed with improved input validation. This issue is fixed in macOS     Monterey 12.4, macOS Big Sur 11.6.6. An application may be able to gain elevated privileges.
    (CVE-2022-26718)

  - An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in Security     Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able     to execute arbitrary code with kernel privileges. (CVE-2022-26720)

  - A memory initialization issue was addressed. This issue is fixed in Security Update 2022-004 Catalina,     macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able to gain root privileges.
    (CVE-2022-26721, CVE-2022-26722)

  - A memory corruption issue was addressed with improved input validation. This issue is fixed in macOS     Monterey 12.4, macOS Big Sur 11.6.6. Mounting a maliciously crafted Samba network share may lead to     arbitrary code execution. (CVE-2022-26723)

  - This issue was addressed with improved checks. This issue is fixed in Security Update 2022-004 Catalina,     watchOS 8.6, macOS Monterey 12.4, macOS Big Sur 11.6.6. An app may be able to capture a user's screen.
    (CVE-2022-26726)

  - This issue was addressed with improved entitlements. This issue is fixed in Security Update 2022-004     Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able to access     restricted files. (CVE-2022-26728)

  - A logic issue was addressed with improved state management. This issue is fixed in macOS Monterey 12.4,     iOS 15.5 and iPadOS 15.5. A malicious website may be able to track users in Safari private browsing mode.
    (CVE-2022-26731)

  - A memory corruption issue was addressed with improved validation. This issue is fixed in macOS Big Sur     11.6.6. A malicious application may disclose restricted memory. (CVE-2022-26745)

  - This issue was addressed by removing the vulnerable code. This issue is fixed in Security Update 2022-004     Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able to bypass Privacy     preferences. (CVE-2022-26746)

  - An out-of-bounds write issue was addressed with improved input validation. This issue is fixed in Security     Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. Processing maliciously crafted web     content may lead to arbitrary code execution. (CVE-2022-26748)

  - A memory corruption issue was addressed with improved input validation. This issue is fixed in iTunes     12.12.4 for Windows, iOS 15.5 and iPadOS 15.5, Security Update 2022-004 Catalina, macOS Big Sur 11.6.6,     macOS Monterey 12.4. Processing a maliciously crafted image may lead to arbitrary code execution.
    (CVE-2022-26751)

  - This issue was addressed with improved environment sanitization. This issue is fixed in Security Update     2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able to break     out of its sandbox. (CVE-2022-26755)

  - An out-of-bounds write issue was addressed with improved input validation. This issue is fixed in Security     Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. An application may be able to execute     arbitrary code with kernel privileges. (CVE-2022-26756)

  - A use after free issue was addressed with improved memory management. This issue is fixed in tvOS 15.5,     iOS 15.5 and iPadOS 15.5, Security Update 2022-004 Catalina, watchOS 8.6, macOS Big Sur 11.6.6, macOS     Monterey 12.4. An application may be able to execute arbitrary code with kernel privileges.
    (CVE-2022-26757)

  - A memory corruption issue was addressed with improved memory handling. This issue is fixed in Security     Update 2022-004 Catalina, macOS Big Sur 11.6.6. An application may be able to execute arbitrary code with     kernel privileges. (CVE-2022-26761)

  - An out-of-bounds access issue was addressed with improved bounds checking. This issue is fixed in tvOS     15.5, iOS 15.5 and iPadOS 15.5, Security Update 2022-004 Catalina, watchOS 8.6, macOS Big Sur 11.6.6,     macOS Monterey 12.4. A malicious application may be able to execute arbitrary code with system privileges.
    (CVE-2022-26763)

  - A certificate parsing issue was addressed with improved checks. This issue is fixed in tvOS 15.5, iOS 15.5     and iPadOS 15.5, Security Update 2022-004 Catalina, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey     12.4. A malicious app may be able to bypass signature validation. (CVE-2022-26766)

  - The issue was addressed with additional permissions checks. This issue is fixed in macOS Monterey 12.4,     macOS Big Sur 11.6.6. A malicious application may be able to bypass Privacy preferences. (CVE-2022-26767)

  - A memory corruption issue was addressed with improved state management. This issue is fixed in macOS     Monterey 12.4, watchOS 8.6, tvOS 15.5, macOS Big Sur 11.6.6. An application may be able to execute     arbitrary code with kernel privileges. (CVE-2022-26768)

  - A memory corruption issue was addressed with improved input validation. This issue is fixed in Security     Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able     to execute arbitrary code with kernel privileges. (CVE-2022-26769)

  - An out-of-bounds read issue was addressed with improved input validation. This issue is fixed in Security     Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able     to execute arbitrary code with kernel privileges. (CVE-2022-26770)

  - This issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.4, macOS Big Sur     11.6.6. An attacker may be able to cause unexpected application termination or arbitrary code execution.
    (CVE-2022-26776)

  - This issue was addressed with improved checks. This issue is fixed in tvOS 15.5, watchOS 8.6, iOS 15.5 and     iPadOS 15.5, macOS Monterey 12.4, macOS Big Sur 11.6.6, Security Update 2022-004 Catalina. A remote user     may be able to cause a denial-of-service. (CVE-2022-32790)

  - A logic issue was addressed with improved state management. This issue is fixed in Security Update     2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. An app may be able to gain elevated     privileges. (CVE-2022-32794)

  - This issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.4, macOS Big Sur     11.6.6. An app may be able to bypass Privacy preferences. (CVE-2022-32882)

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2022-1743 advisory.

    vim is vulnerable to Heap-based Buffer Overflow (CVE-2021-3903)

    A flaw was found in vim. A possible heap-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. The highest threat from this vulnerability is     to data confidentiality and integrity as well as system availability. (CVE-2021-3927)

    A flaw was found in vim. A possible stack-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. The highest threat from this vulnerability is     to data confidentiality and integrity as well as system availability. (CVE-2021-3928)

    A flaw was found in vim. A possible heap-based buffer overflow allows an attacker to input a specially     crafted file, leading to a crash or code execution. The highest threat from this vulnerability is     confidentiality, integrity, and system availability. (CVE-2021-3984)

    A flaw was found in vim. A possible heap-based buffer overflow vulnerability allows an attacker to input a     specially crafted file, leading to a crash or code execution. The highest threat from this vulnerability     is system availability. (CVE-2021-4019)

    vim is vulnerable to Use After Free (CVE-2021-4069)

    A flaw was found in vim. A possible heap-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. (CVE-2021-4136)

    A flaw was found in vim. A possible heap-based buffer overflow could allow an attacker to input a     specially crafted file leading to a crash or code execution. (CVE-2021-4166)

    A flaw was found in vim. A possible use after free vulnerability could allow an attacker to input a     specially crafted file leading to a crash or code execution. (CVE-2021-4173)

    A flaw was found in vim. A possible use after free vulnerability could allow an attacker to input a     specially crafted file leading to a crash or code execution. (CVE-2021-4187)

    It was found that vim was vulnerable to use-after-free flaw in win_linetabsize(). Sourcing a specially     crafted file in vim could crash the vim process or possibly lead to other undefined behaviors.
    (CVE-2021-4192)

    It was found that vim was vulnerable to an out-of-bound read flaw in getvcol(). A specially crafted file     could be used to, when opened in vim, disclose some of the process's internal memory. (CVE-2021-4193)

    References to CVE-2021-4192 and CVE-2021-4193 have been added after the original release of this advisory,     however those vulnerabilities were fixed by the packages referenced by this advisory's initial release on     2022-01-18.

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - vim is vulnerable to Out-of-bounds Read (CVE-2021-4166)

Note that Nessus relies on the presence of the package as reported by the vendor.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2022-2022-155 advisory.

    A use-after-free vulnerability was found in vim's do_cmdline() function of the src/ex_docmd.c file. The     issue triggers when an invalid line number on :for is ignored. This flaw allows an attacker to trick a     user into opening a specially crafted file, triggering use-after-free that causes an application to crash,     possibly executing code and corrupting memory. (CVE-2022-3099)

    A heap use-after-free vulnerability was found in vim's do_tag() function of the src/tag.c file. The issue     triggers when the 'tagfunc' closes the window. This flaw allows an attacker to trick a user into opening a     specially crafted file, triggering a heap use-after-free that causes an application to crash, possibly     executing code and corrupting memory. (CVE-2022-3134)

    NULL Pointer Dereference in GitHub repository vim/vim prior to 9.0.0404. (CVE-2022-3153)

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
156877	Amazon Linux AMI : vim (ALAS-2022-1557)	Nessus	Amazon Linux Local Security Checks	2022/1/20	2024/12/11	critical
169350	SUSE SLES12 Security Update : vim (SUSE-SU-2022:4619-1)	Nessus	SuSE Local Security Checks	2022/12/28	2026/6/26	critical
159106	macOS 12.x < 12.3 (HT213183)	Nessus	MacOS X Local Security Checks	2022/3/21	2024/5/28	critical
163127	EulerOS Virtualization 2.10.0 : vim (EulerOS-SA-2022-2042)	Nessus	Huawei Local Security Checks	2022/7/14	2023/10/18	critical
159775	EulerOS 2.0 SP9 : vim (EulerOS-SA-2022-1441)	Nessus	Huawei Local Security Checks	2022/4/18	2023/11/1	critical
159979	EulerOS 2.0 SP10 : vim (EulerOS-SA-2022-1499)	Nessus	Huawei Local Security Checks	2022/4/20	2023/11/1	high
160627	EulerOS Virtualization 2.9.0 : vim (EulerOS-SA-2022-1641)	Nessus	Huawei Local Security Checks	2022/5/5	2023/10/30	critical
203190	Photon OS 4.0: Vim PHSA-2022-4.0-0153	Nessus	PhotonOS Local Security Checks	2024/7/23	2024/7/23	critical
203964	Photon OS 3.0: Vim PHSA-2022-3.0-0358	Nessus	PhotonOS Local Security Checks	2024/7/24	2024/7/24	critical
161395	macOS 11.x < 11.6.6 Multiple Vulnerabilities (HT213256)	Nessus	MacOS X Local Security Checks	2022/5/20	2024/8/20	critical
158046	Amazon Linux 2 : vim, --advisory ALAS2-2022-1743 (ALAS-2022-1743)	Nessus	Amazon Linux Local Security Checks	2022/2/14	2025/9/30	high
224235	Linux Distros Unpatched Vulnerability : CVE-2021-4166	Nessus	Misc.	2025/3/5	2026/9/2	high
166352	Amazon Linux 2022 : vim-common, vim-data, vim-default-editor (ALAS2022-2022-155)	Nessus	Amazon Linux Local Security Checks	2022/10/20	2024/12/11	critical

检测

插件搜索

critical

critical

critical

critical

critical

high

critical

critical

critical

critical

high

high

critical