Debian Patches
Status for vim/2:9.0.1378-2+deb12u2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch | Support sourcing a vimrc.tiny when Vim is invoked as vi This is used only in the vim-tiny package to allow a specific configuration for vim-tiny's vi. The vim-tiny package is substantially different from other Vim packages, so it does not make sense to share the same config. |
James McCoy <jamessan@debian.org> | no | 2015-10-06 | ||
| debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch | Detect the rst filetype using the contents of the file | James Vega <jamessan@debian.org> | no | 2006-08-18 | ||
| debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch | Add recognition of more LaTeX commands for tex filetype detection Since filetype detection of TeX files defaults to plaintex, we've added detection of some additional LaTeX commands to help sway the detection to LaTeX. |
Stefano Zacchiroli <zack@debian.org> | no | 2006-08-25 | ||
| debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch | Document Debian's decision to disable modelines by default Modelines have historically been a source of vulnerabilities in Vim. As long as it remains a "blacklist suspected/proven dangerous options" instead of a "whitelist allowed options" piece of functionality, Debian's system-wide vimrc will maintain this setting. As such, the documentation needs to be updated to reflect the induced behavior. |
James Vega <jamessan@debian.org> | no | 2008-03-27 | ||
| patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch | patch 9.0.1499: using uninitialized memory with fuzzy matching | Bram Moolenaar <Bram@vim.org> | no | 2023-04-29 | ||
| Fix-GH-267-where-indent-after-a-sub-would-not-work.patch | Fix GH#267 where indent after a sub would not work | Andy Lester <andy@petdance.com> | no | 2022-04-26 | ||
| CVE-2023-2610.patch | patch 9.0.1532: crash when expanding "~" in substitute causes very long text (cherry picked from commit ab9a2d884b3a4abe319606ea95a5a6d6b01cd73a) |
Bram Moolenaar <Bram@vim.org> | no | 2023-05-09 | ||
| CVE-2023-4738.patch | patch 9.0.1848: [security] buffer-overflow in vim_regsub_both() (cherry picked from commit ced2c7394aafdc90fb7845e09b3a3fee23d48cb1) |
Christian Brabandt <cb@256bit.org> | no | 2023-09-02 | ||
| CVE-2023-4752.patch | patch 9.0.1858: [security] heap use after free in ins_compl_get_exp() (cherry picked from commit ee9166eb3b41846661a39b662dc7ebe8b5e15139) |
Christian Brabandt <cb@256bit.org> | no | 2023-09-03 | ||
| CVE-2023-4781.patch | patch 9.0.1873: [security] heap-buffer-overflow in vim_regsub_both (cherry picked from commit f6d28fe2c95c678cc3202cc5dc825a3fcc709e93) |
Christian Brabandt <cb@256bit.org> | no | 2023-09-05 | ||
| CVE-2023-5344.patch | patch 9.0.1969: [security] buffer-overflow in trunc_string() Currently trunc_string() assumes that when the string is too long, buf[e-1] will always be writeable. But that assumption may not always be true. The condition currently looks like this else if (e + 3 < buflen) [...] else { // can't fit in the "...", just truncate it buf[e - 1] = NUL; } but this means, we may run into the last else clause with e still being larger than buflen. So a buffer overflow occurs. So instead of using `buf[e - 1]`, let's just always truncate at `buf[buflen - 1]` which should always be writable. (cherry picked from commit 3bd7fa12e146c6051490d048a4acbfba974eeb04) |
Christian Brabandt <cb@256bit.org> | no | 2023-10-02 | ||
| CVE-2024-22667.patch | patch 9.0.2142: [security]: stack-buffer-overflow in option callback functions instead of sprintf() We pass the error buffer down to the option callback functions, but in some parts of the code, we simply use sprintf(buf) to write into the error buffer, which can overflow. So let's pass down the length of the error buffer and use sprintf(buf, size) instead. Reported by @henices, thanks! (cherry picked from commit b39b240c386a5a29241415541f1c99e2e6b8ce47) |
Christian Brabandt <cb@256bit.org> | no | 2023-11-29 | ||
| CVE-2024-43802.patch | patch 9.1.0697: [security]: heap-buffer-overflow in ins_typebuf (SuyueGuo) is enough space left Github Advisory: https://github.com/vim/vim/security/advisories/GHSA-4ghr-c62x-cqfh (cherry picked from commit 322ba9108612bead5eb7731ccb66763dec69ef1b) |
Christian Brabandt <cb@256bit.org> | no | 2024-08-25 | ||
| CVE-2024-47814.patch | patch 9.1.0764: [security]: use-after-free when closing a buffer check whether the newly to be edited buffer has been marked for deletion and abort in this case Github Advisory: https://github.com/vim/vim/security/advisories/GHSA-rj48-v4mq-j4vg (cherry picked from commit 51b62387be93c65fa56bbabe1c3c1ea5df187641) |
Christian Brabandt <cb@256bit.org> | no | 2024-10-06 |
All known versions for source package 'vim'
- 2:9.1.1113-1 (sid, trixie)
- 2:9.0.1378-2+deb12u2 (bookworm-proposed-updates)
- 2:9.0.1378-2 (bookworm)
- 2:8.2.2434-3+deb11u1 (bullseye)