Overview 292 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 10 public PoC · 0 EPSS ≥ 0.5
292matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
10public PoC3.4%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
1
0.3%
Not applicable
291
99.7%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
292
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
10
3.4%
Proof of concept only
48
16.4%
Forecast only
0
0.0%
No public exploit
234
80.1%
split by
peak 115 / year
20012
Not applicable2
Medium1
Low1
not blocked2
Working exploit published1
No public exploit1
20021
Not applicable1
Medium1
not blocked1
No public exploit1
20030
20040
20053
Not applicable3
High2
Medium1
not blocked3
No public exploit3
20060
20074
Not applicable4
High2
Medium2
not blocked4
Working exploit published1
No public exploit3
20086
Not applicable6
High4
Medium1
Low1
not blocked6
Working exploit published5
No public exploit1
20095
Not applicable5
High4
Medium1
not blocked5
Working exploit published1
No public exploit4
20101
Not applicable1
High1
not blocked1
No public exploit1
20110
20120
20130
20142
Not applicable2
High2
not blocked2
No public exploit2
20150
20163
Not applicable3
High3
not blocked3
No public exploit3
20179
Not applicable9
Critical3
High2
Medium4
not blocked9
Working exploit published1
No public exploit8
20180
20193
Not applicable3
High2
Medium1
not blocked3
Working exploit published1
No public exploit2
20202
Not applicable2
High1
Medium1
not blocked2
No public exploit2
202121
Not applicable21
High19
Medium2
not blocked21
No public exploit21
2022115
Outside Waratek scope1
Not applicable114
Critical2
High94
Medium18
Low1
not blocked115
Proof of concept only12
No public exploit103
202345
Not applicable45
Critical1
High24
Medium20
not blocked45
Proof of concept only30
No public exploit15
202410
Not applicable10
High3
Medium7
not blocked10
Proof of concept only1
No public exploit9
202513
Not applicable13
High2
Medium8
Low3
not blocked13
Proof of concept only5
No public exploit8
202647
Not applicable47
Critical1
High23
Medium21
Low2
not blocked47
No public exploit47
200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-1420 | Medium | 2022-04-21 | Not applicable | No public exploit | Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4774. |
| CVE-2022-1381 | High | 2022-04-18 | Not applicable | No public exploit | global heap buffer overflow in skip_range in GitHub repository vim/vim prior to 8.2.4763. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution |
| CVE-2022-1160 | High | 2022-03-30 | Not applicable | No public exploit | heap buffer overflow in get_one_sourceline in GitHub repository vim/vim prior to 8.2.4647. |
| CVE-2022-1154 | High | 2022-03-30 | Not applicable | No public exploit | Use after free in utf_ptr2char in GitHub repository vim/vim prior to 8.2.4646. |
| CVE-2022-0943 | High | 2022-03-14 | Not applicable | No public exploit | Heap-based Buffer Overflow occurs in vim in GitHub repository vim/vim prior to 8.2.4563. |
| CVE-2022-0729 | High | 2022-02-23 | Not applicable | No public exploit | Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4440. |
| CVE-2022-0714 | Medium | 2022-02-22 | Not applicable | No public exploit | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436. |
| CVE-2022-0696 | Medium | 2022-02-21 | Not applicable | No public exploit | NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2.4428. |
| CVE-2022-0685 | High | 2022-02-20 | Not applicable | No public exploit | Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4418. |
| CVE-2022-0629 | High | 2022-02-17 | Not applicable | No public exploit | Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0572 | High | 2022-02-14 | Not applicable | No public exploit | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0554 | High | 2022-02-10 | Not applicable | No public exploit | Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0443 | High | 2022-02-02 | Not applicable | No public exploit | Use After Free in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0417 | High | 2022-02-01 | Not applicable | No public exploit | Heap-based Buffer Overflow GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0413 | High | 2022-01-30 | Not applicable | No public exploit | Use After Free in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0408 | High | 2022-01-30 | Not applicable | No public exploit | Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0407 | High | 2022-01-30 | Not applicable | No public exploit | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0393 | High | 2022-01-28 | Not applicable | No public exploit | Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0392 | High | 2022-01-28 | Not applicable | No public exploit | Heap-based Buffer Overflow in GitHub repository vim prior to 8.2. |
| CVE-2022-0368 | High | 2022-01-26 | Not applicable | No public exploit | Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0361 | High | 2022-01-26 | Not applicable | No public exploit | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0359 | High | 2022-01-26 | Not applicable | No public exploit | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0351 | High | 2022-01-25 | Not applicable | No public exploit | Access of Memory Location Before Start of Buffer in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0319 | Medium | 2022-01-21 | Not applicable | No public exploit | Out-of-bounds Read in vim/vim prior to 8.2. |
| CVE-2022-0318 | Critical | 2022-01-21 | Not applicable | No public exploit | Heap-based Buffer Overflow in vim/vim prior to 8.2. |
| CVE-2022-0261 | High | 2022-01-18 | Not applicable | No public exploit | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. |
| CVE-2022-0213 | Medium | 2022-01-14 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2022-0158 | Low | 2022-01-10 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2022-0156 | Medium | 2022-01-10 | Not applicable | No public exploit | vim is vulnerable to Use After Free |
| CVE-2022-0128 | High | 2022-01-06 | Not applicable | No public exploit | vim is vulnerable to Out-of-bounds Read |
| CVE-2021-4193 | Medium | 2021-12-31 | Not applicable | No public exploit | vim is vulnerable to Out-of-bounds Read |
| CVE-2021-4192 | High | 2021-12-31 | Not applicable | No public exploit | vim is vulnerable to Use After Free |
| CVE-2021-4187 | High | 2021-12-29 | Not applicable | No public exploit | vim is vulnerable to Use After Free |
| CVE-2021-4173 | High | 2021-12-27 | Not applicable | No public exploit | vim is vulnerable to Use After Free |
| CVE-2021-4166 | High | 2021-12-25 | Not applicable | No public exploit | vim is vulnerable to Out-of-bounds Read |
| CVE-2021-4136 | High | 2021-12-19 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-4069 | High | 2021-12-06 | Not applicable | No public exploit | vim is vulnerable to Use After Free |
| CVE-2021-4019 | High | 2021-12-01 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3984 | High | 2021-12-01 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3974 | High | 2021-11-19 | Not applicable | No public exploit | vim is vulnerable to Use After Free |
| CVE-2021-3973 | High | 2021-11-19 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3968 | High | 2021-11-19 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3928 | High | 2021-11-05 | Not applicable | No public exploit | vim is vulnerable to Use of Uninitialized Variable |
| CVE-2021-3927 | High | 2021-11-05 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3903 | High | 2021-10-27 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3872 | High | 2021-10-19 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3875 | Medium | 2021-10-15 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3796 | High | 2021-09-15 | Not applicable | No public exploit | vim is vulnerable to Use After Free |
| CVE-2021-3778 | High | 2021-09-15 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-3770 | High | 2021-09-06 | Not applicable | No public exploit | vim is vulnerable to Heap-based Buffer Overflow |
| CVE-2021-28832 | High | 2021-04-05 | Not applicable | No public exploit | VSCodeVim before 1.19.0 allows attackers to execute arbitrary code via a crafted workspace configuration. |
| CVE-2020-27623 | High | 2020-11-16 | Not applicable | No public exploit | JetBrains IdeaVim before version 0.58 might have caused an information leak in limited circumstances. |
| CVE-2019-20807 | Medium | 2020-05-28 | Not applicable | No public exploit | In Vim before 8.1.0881, users can circumvent the rvim restricted mode and execute arbitrary OS commands via scripting interfaces (e.g., Python, Ruby, or Lua). |
| CVE-2019-20079 | High | 2019-12-30 | Not applicable | No public exploit | The autocmd feature in window.c in Vim before 8.1.2136 accesses freed memory. |
| CVE-2019-14957 | Medium | 2019-10-01 | Not applicable | No public exploit | The JetBrains Vim plugin before version 0.52 was storing individual project data in the global vim_settings.xml file. This xml file could be synchronized to a publicly accessible GitHub repository. |
| CVE-2019-12735 | High | 2019-06-05 | Not applicable | Working exploit published | getchar.c in Vim before 8.1.1365 and Neovim before 0.3.6 allows remote attackers to execute arbitrary OS commands via the :source! command in a modeline, as demonstrated by execute in Vim, and assert_fails or nvim_input in Neovim. |
| CVE-2017-17087 | Medium | 2017-12-01 | Not applicable | No public exploit | fileio.c in Vim prior to 8.0.1263 sets the group ownership of a .swp file to the editor's primary group (which may be different from the group ownership of the original file), which allows local users to obtain sensitive information by leveraging an applicable group membership, as demonstrated by /etc/shadow owned by root:shadow mode 0640, but /etc/.shadow.swp owned by root:users mode 0640, a different vulnerability than CVE-2017-1000382. |
| CVE-2017-1000382 | Medium | 2017-10-31 | Not applicable | No public exploit | VIM version 8.0.1187 (and other versions most likely) ignores umask when creating a swap file ("[ORIGINAL_FILENAME].swp") resulting in files that may be world readable or otherwise accessible in ways not intended by the user running the vi binary. |
| CVE-2017-11109 | High | 2017-07-08 | Not applicable | No public exploit | Vim 8.0 allows attackers to cause a denial of service (invalid free) or possibly have unspecified other impact via a crafted source (aka -S) file. NOTE: there might be a limited number of scenarios in which this has security relevance. |
| CVE-2017-6086 | High | 2017-06-27 | Not applicable | Working exploit published | Multiple cross-site request forgery (CSRF) vulnerabilities in the addAction and purgeAction functions in ViMbAdmin 3.0.15 allow remote attackers to hijack the authentication of logged administrators to (1) add an administrator user via a crafted POST request to <vimbadmin directory>/application/controllers/DomainController.php, (2) remove an administrator user via a crafted GET request to <vimbadmin directory>/application/controllers/DomainController.php, (3) change an administrator password via a crafted POST request to <vimbadmin directory>/application/controllers/DomainController.php, (4) add a mailbox via a crafted POST request to <vimbadmin directory>/application/controllers/MailboxController.php, (5) delete a mailbox via a crafted POST request to <vimbadmin directory>/application/controllers/MailboxController.php, (6) archive a mailbox address via a crafted GET request to <vimbadmin directory>/application/controllers/ArchiveController.php, (7) add an alias address via a crafted POST request to <vimbadmin directory>/application/controllers/AliasController.php, or (8) remove an alias address via a crafted GET request to <vimbadmin directory>/application/controllers/AliasController.php. |
| CVE-2017-5870 | Medium | 2017-05-23 | Not applicable | No public exploit | Multiple cross-site scripting (XSS) vulnerabilities in ViMbAdmin 3.0.15 allow remote attackers to inject arbitrary web script or HTML via the (1) domain or (2) transport parameter to domain/add; the (3) name parameter to mailbox/add/did/<domain id>; the (4) goto parameter to alias/add/did/<domain id>; or the (5) captchatext parameter to auth/lost-password. |
| CVE-2017-6350 | Critical | 2017-02-27 | Not applicable | No public exploit | An integer overflow at an unserialize_uep memory allocation site would occur for vim before patch 8.0.0378, if it does not properly validate values for tree length when reading a corrupted undo file, which may lead to resultant buffer overflows. |
| CVE-2017-6349 | Critical | 2017-02-27 | Not applicable | No public exploit | An integer overflow at a u_read_undo memory allocation site would occur for vim before patch 8.0.0377, if it does not properly validate values for tree length when reading a corrupted undo file, which may lead to resultant buffer overflows. |
| CVE-2017-5953 | Critical | 2017-02-10 | Not applicable | No public exploit | vim before patch 8.0.0322 does not properly validate values for tree length when handling a spell file, which may result in an integer overflow at a memory allocation site and a resultant buffer overflow. |
| CVE-2017-5605 | Medium | 2017-02-09 | Not applicable | No public exploit | An incorrect implementation of "XEP-0280: Message Carbons" in multiple XMPP clients allows a remote attacker to impersonate any user, including contacts, in the vulnerable application's display. This allows for various kinds of social engineering attacks. This CVE is for Movim 0.8 - 0.10. |
| CVE-2016-1248 | High | 2016-11-23 | Not applicable | No public exploit | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. |
| CVE-2016-2294 | High | 2016-04-21 | Not applicable | No public exploit | The AXM-NET module in Accuenergy Acuvim II NET Firmware 3.08 and Acuvim IIR NET Firmware 3.08 allows remote attackers to discover a cleartext mail-server password via unspecified vectors. |
| CVE-2016-2293 | High | 2016-04-21 | Not applicable | No public exploit | The AXM-NET module in Accuenergy Acuvim II NET Firmware 3.08 and Acuvim IIR NET Firmware 3.08 allows remote attackers to discover settings via a direct request to an unspecified URL. |
| CVE-2014-2374 | High | 2014-11-05 | Not applicable | No public exploit | The AXN-NET Ethernet module accessory 3.04 for the Accuenergy Acuvim II allows remote attackers to discover passwords and modify settings via vectors involving JavaScript. |
| CVE-2014-2373 | High | 2014-11-05 | Not applicable | No public exploit | The AXN-NET Ethernet module accessory 3.04 for the Accuenergy Acuvim II allows remote attackers to discover passwords and modify settings via vectors involving JavaScript. |
| CVE-2010-3914 | High | 2010-11-03 | Not applicable | No public exploit | Untrusted search path vulnerability in VIM Development Group GVim before 7.3.034, and possibly other versions before 7.3.46, allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse User32.dll or other DLL that is located in the same folder as a .TXT file. NOTE: some of these details are obtained from third party information. |
| CVE-2008-6235 | High | 2009-02-21 | Not applicable | No public exploit | The Netrw plugin (netrw.vim) in Vim 7.0 and 7.1 allows user-assisted attackers to execute arbitrary commands via shell metacharacters in a filename used by the (1) "D" (delete) command or (2) b:netrw_curdir variable, as demonstrated using the netrw.v4 and netrw.v5 test cases. |
| CVE-2008-3076 | High | 2009-02-21 | Not applicable | Working exploit published | The Netrw plugin 125 in netrw.vim in Vim 7.2a.10 allows user-assisted attackers to execute arbitrary code via shell metacharacters in filenames used by the execute and system functions within the (1) mz and (2) mc commands, as demonstrated by the netrw.v2 and netrw.v3 test cases. NOTE: this issue reportedly exists because of an incomplete fix for CVE-2008-2712. |
| CVE-2008-3075 | High | 2009-02-21 | Not applicable | No public exploit | The shellescape function in Vim 7.0 through 7.2, including 7.2a.10, allows user-assisted attackers to execute arbitrary code via the "!" (exclamation point) shell metacharacter in (1) the filename of a ZIP archive and possibly (2) the filename of the first file in a ZIP archive, which is not properly handled by zip.vim in the VIM ZIP plugin (zipPlugin.vim) v.11 through v.21, as demonstrated by the zipplugin and zipplugin.v2 test cases. NOTE: this issue reportedly exists because of an incomplete fix for CVE-2008-2712. NOTE: this issue has the same root cause as CVE-2008-3074. NOTE: due to the complexity of the associated disclosures and the incomplete information related to them, there may be inaccuracies in this CVE description and in external mappings to this identifier. |
| CVE-2008-3074 | High | 2009-02-21 | Not applicable | No public exploit | The shellescape function in Vim 7.0 through 7.2, including 7.2a.10, allows user-assisted attackers to execute arbitrary code via the "!" (exclamation point) shell metacharacter in (1) the filename of a tar archive and possibly (2) the filename of the first file in a tar archive, which is not properly handled by the VIM TAR plugin (tar.vim) v.10 through v.22, as demonstrated by the shellescape, tarplugin.v2, tarplugin, and tarplugin.updated test cases. NOTE: this issue reportedly exists because of an incomplete fix for CVE-2008-2712. NOTE: this issue has the same root cause as CVE-2008-3075. NOTE: due to the complexity of the associated disclosures and the incomplete information related to them, there may be inaccuracies in this CVE description and in external mappings to this identifier. |
| CVE-2009-0316 | Medium | 2009-01-28 | Not applicable | No public exploit | Untrusted search path vulnerability in src/if_python.c in the Python interface in Vim before 7.2.045 allows local users to execute arbitrary code via a Trojan horse Python file in the current working directory, related to a vulnerability in the PySys_SetArgv function (CVE-2008-5983), as demonstrated by an erroneous search path for plugin/bike.vim in bicyclerepair. |
| CVE-2008-4750 | High | 2008-10-27 | Not applicable | Working exploit published | Stack-based buffer overflow in the VImpX.VImpAX ActiveX control (VImpX.ocx) 4.8.8.0 in DB Software Laboratory VImp X, possibly 4.7.7, allows remote attackers to execute arbitrary code via a long LogFile property. |
| CVE-2008-4749 | High | 2008-10-27 | Not applicable | Working exploit published | Multiple insecure method vulnerabilities in the VImpX.VImpAX ActiveX control (VImpX.ocx) 4.8.8.0 in DB Software Laboratory VImp X, possibly 4.7.7, allow remote attackers to overwrite arbitrary files via (1) the LogFile property and ClearLogFile method, and (2) the SaveToFile method. |
| CVE-2008-3432 | Medium | 2008-10-10 | Not applicable | Working exploit published | Heap-based buffer overflow in the mch_expand_wildcards function in os_unix.c in Vim 6.2 and 6.3 allows user-assisted attackers to execute arbitrary code via shell metacharacters in filenames, as demonstrated by the netrw.v3 test case. |
| CVE-2008-4101 | High | 2008-09-18 | Not applicable | Working exploit published | Vim 3.0 through 7.x before 7.2.010 does not properly escape characters, which allows user-assisted attackers to (1) execute arbitrary shell commands by entering a K keystroke on a line that contains a ";" (semicolon) followed by a command, or execute arbitrary Ex commands by entering an argument after a (2) "Ctrl-]" (control close-square-bracket) or (3) "g]" (g close-square-bracket) keystroke sequence, a different issue than CVE-2008-2712. |
| CVE-2008-3294 | Low | 2008-07-24 | Not applicable | No public exploit | src/configure.in in Vim 5.0 through 7.1, when used for a build with Python support, does not ensure that the Makefile-conf temporary file has the intended ownership and permissions, which allows local users to execute arbitrary code by modifying this file during a time window, or by creating it ahead of time with permissions that prevent its modification by configure. |
| CVE-2008-2712 | High | 2008-06-16 | Not applicable | Working exploit published | Vim 7.1.314, 6.4, and other versions allows user-assisted remote attackers to execute arbitrary commands via Vim scripts that do not properly sanitize inputs before invoking the execute or system functions, as demonstrated using (1) filetype.vim, (3) xpm.vim, (4) gzip_vim, and (5) netrw. NOTE: the originally reported version was 7.1.314, but the researcher actually found this set of issues in 7.1.298. NOTE: the zipplugin issue (originally vector 2 in this identifier) has been subsumed by CVE-2008-3075. |
| CVE-2007-5445 | Medium | 2007-10-14 | Not applicable | No public exploit | Buffer overflow in the DB Software Laboratory VImpX (VImpAX1) ActiveX control in VImpX.ocx 4.7.3.0 allows remote attackers to execute arbitrary code via a long RejectedRecordsFile parameter, a different vector than CVE-2007-2667. |
| CVE-2007-2953 | Medium | 2007-07-31 | Not applicable | No public exploit | Format string vulnerability in the helptags_one function in src/ex_cmds.c in Vim 6.4 and earlier, and 7.x up to 7.1, allows user-assisted remote attackers to execute arbitrary code via format string specifiers in a help-tags tag in a help file, related to the helptags command. |
| CVE-2007-2667 | High | 2007-05-14 | Not applicable | Working exploit published | Buffer overflow in the DB Software Laboratory VImpX ActiveX control in VImpX.ocx 4.7.3 allows remote attackers to execute arbitrary code via a long LogFile parameter. |
| CVE-2007-2438 | High | 2007-05-02 | Not applicable | No public exploit | The sandbox for vim allows dangerous functions such as (1) writefile, (2) feedkeys, and (3) system, which might allow user-assisted attackers to execute shell commands and write files via modelines. |
| CVE-2005-2368 | High | 2005-07-26 | Not applicable | No public exploit | vim 6.3 before 6.3.082, with modelines enabled, allows external user-assisted attackers to execute arbitrary commands via shell metacharacters in the (1) glob or (2) expand commands of a foldexpr expression for calculating fold levels. |
| CVE-2005-0069 | Medium | 2005-01-13 | Not applicable | No public exploit | The (1) tcltags or (2) vimspell.sh scripts in vim 6.3 allow local users to overwrite or create arbitrary files via a symlink attack on temporary files. |
| CVE-2004-1138 | High | 2005-01-10 | Not applicable | No public exploit | VIM before 6.3 and gVim before 6.3 allow local users to execute arbitrary commands via a file containing a crafted modeline that is executed when the file is viewed using options such as (1) termcap, (2) printdevice, (3) titleold, (4) filetype, (5) syntax, (6) backupext, (7) keymap, (8) patchmode, or (9) langmenu. |
| CVE-2002-1377 | Medium | 2002-12-23 | Not applicable | No public exploit | vim 6.0 and 6.1, and possibly other versions, allows attackers to execute arbitrary commands using the libcall feature in modelines, which are not sandboxed but may be executed when vim is used to edit a malicious file, as demonstrated using mutt. |
| CVE-2001-0409 | Low | 2001-06-18 | Not applicable | Working exploit published | vim (aka gvim) allows local users to modify files being edited by other users via a symlink attack on the backup and swap files, when the victim is editing the file in a world writable directory. |
| CVE-2001-0408 | Medium | 2001-06-18 | Not applicable | No public exploit | vim (aka gvim) processes VIM control codes that are embedded in a file, which could allow attackers to execute arbitrary commands when another user opens a file containing malicious VIM control codes. |