diff options
| author | zeertzjq <zeertzjq@outlook.com> | 2023-10-17 22:43:42 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-17 22:43:42 +0800 |
| commit | 272ef271153b0f66410b0e59ce31e05d211b44fd (patch) | |
| tree | b332c1967573259490034efaefb5092067e8923f /runtime/lua/vim/_meta/options.lua | |
| parent | 356a6728ac077fa7ec4f6fbc51eda33e025d86e0 (diff) | |
| download | rneovim-272ef271153b0f66410b0e59ce31e05d211b44fd.tar.gz rneovim-272ef271153b0f66410b0e59ce31e05d211b44fd.tar.bz2 rneovim-272ef271153b0f66410b0e59ce31e05d211b44fd.zip | |
vim-patch:9.0.2035: [security] use-after-free with wildmenu (#25687)
Problem: [security] use-after-free with wildmenu
Solution: properly clean up the wildmenu when exiting
Fix wildchar/wildmenu/pum memory corruption with special wildchar's
Currently, using `wildchar=<Esc>` or `wildchar=<C-\>` can lead to a
memory corruption if using wildmenu+pum, or wrong states if only using
wildmenu. This is due to the code only using one single place inside the
cmdline process loop to perform wild menu clean up (by checking
`end_wildmenu`) but there are other odd situations where the loop could
have exited and we need a post-loop clean up just to be sure. If the
clean up was not done you would have a stale popup menu referring to
invalid memory, or if not using popup menu, incorrect status line (if
`laststatus=0`).
For example, if you hit `<Esc>` two times when it's wildchar, there's a
hard-coded behavior to exit command-line as a failsafe for user, and if
you hit `<C-\><C-\><C-N>` it will also exit command-line, but the clean
up code would not have hit because of specialized `<C-\>` handling.
Fix Ctrl-E / Ctrl-Y to not cancel/accept wildmenu if they are also
used for 'wildchar'/'wildcharm'. Currently they don't behave properly,
and also have potentially memory unsafe behavior as the logic is
currently not accounting for this situation and try to do both.
(Previous patch that addressed this: vim/vim#11677)
Also, correctly document Escape key behavior (double-hit it to escape)
in wildchar docs as it's previously undocumented.
In addition, block known invalid chars to be set in `wildchar` option,
such as Ctrl-C and `<CR>`. This is just to make it clear to the user
they shouldn't be set, and is not required for this bug fix.
closes: vim/vim#13361
https://github.com/vim/vim/commit/8f4fb007e4d472b09ff6bed9ffa485e0c3093699
Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com>
Diffstat (limited to 'runtime/lua/vim/_meta/options.lua')
| -rw-r--r-- | runtime/lua/vim/_meta/options.lua | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/runtime/lua/vim/_meta/options.lua b/runtime/lua/vim/_meta/options.lua index 50146bac50..cc013112b3 100644 --- a/runtime/lua/vim/_meta/options.lua +++ b/runtime/lua/vim/_meta/options.lua @@ -7466,6 +7466,8 @@ vim.go.ww = vim.go.whichwrap --- The character is not recognized when used inside a macro. See --- 'wildcharm' for that. --- Some keys will not work, such as CTRL-C, <CR> and Enter. +--- <Esc> can be used, but hitting it twice in a row will still exit +--- command-line as a failsafe measure. --- Although 'wc' is a number option, you can set it to a special key: --- ``` --- :set wc=<Tab> |