A flaw has been found in Neovim up to 0.12.2. Affected by this issue is the function M.read of the file runtime/lua/vim/secure.lua of the component View Branch. Executing a manipulation of the argument path can lead to command injection. It is possible to launch the attack on the...
Product
debian/neovim vulnerabilities
7 published CVES affecting debian/neovim, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 3
- High
- 2
- Medium
- 1
- Low
- 0
- Unscored
- 1
- CISA KEV
- 0
Latest debian/neovim CVEs
Newest publication first
-
MediumCVSS 4.8 EPSS 1.0%
-
DSA-4487-1 neovim - security update
PublishedUnknown -
HighCVSS 8.6 EPSS 19.0% Public exploit
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.
-
CriticalCVSS 9.8 EPSS 3.2%
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.
-
CriticalCVSS 9.8 EPSS 2.7%
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.
-
CriticalCVSS 9.8 EPSS 2.8%
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.
-
HighCVSS 7.8 EPSS 25.3%
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.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.