Overview 262 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 5 public PoC · 0 EPSS ≥ 0.5
262matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
5public PoC1.9%
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.4%
Not applicable
261
99.6%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
262
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
5
1.9%
Proof of concept only
45
17.2%
Forecast only
0
0.0%
No public exploit
212
80.9%
split by
peak 115 / year
20085
Not applicable5
High2
Medium2
Low1
not blocked5
Working exploit published3
No public exploit2
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
20140
20150
20161
Not applicable1
High1
not blocked1
No public exploit1
20176
Not applicable6
Critical3
High1
Medium2
not blocked6
No public exploit6
20180
20192
Not applicable2
High2
not blocked2
Working exploit published1
No public exploit1
20201
Not applicable1
Medium1
not blocked1
No public exploit1
202120
Not applicable20
High18
Medium2
not blocked20
No public exploit20
2022115
Outside Waratek scope1
Not applicable114
Critical2
High94
Medium18
Low1
not blocked115
Proof of concept only12
No public exploit103
202339
Not applicable39
Critical1
High21
Medium17
not blocked39
Proof of concept only27
No public exploit12
20247
Not applicable7
High1
Medium6
not blocked7
Proof of concept only1
No public exploit6
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
2008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-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-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-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-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-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-4677 | Medium | 2008-10-22 | Not applicable | No public exploit | autoload/netrw.vim (aka the Netrw Plugin) 109, 131, and other versions before 133k for Vim 7.1.266, other 7.1 versions, and 7.2 stores credentials for an FTP session, and sends those credentials when attempting to establish subsequent FTP sessions to servers on different hosts, which allows remote FTP servers to obtain sensitive information in opportunistic circumstances by logging usernames and passwords. NOTE: the upstream vendor disputes a vector involving different ports on the same host, stating "I'm assuming that they're using the same id and password on that unchanged hostname, deliberately." |
| 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. |