[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[SECURITY] [DLA 3182-1] vim security update



-------------------------------------------------------------------------
Debian LTS Advisory DLA-3182-1                debian-lts@lists.debian.org
https://www.debian.org/lts/security/                      Markus Koschany
November 08, 2022                             https://wiki.debian.org/LTS
-------------------------------------------------------------------------

Package        : vim
Version        : 2:8.1.0875-5+deb10u3
CVE ID         : CVE-2021-3927 CVE-2021-3928 CVE-2021-3974 CVE-2021-3984 
                 CVE-2021-4019 CVE-2021-4069 CVE-2021-4192 CVE-2021-4193 
                 CVE-2022-0213 CVE-2022-0261 CVE-2022-0319 CVE-2022-0351 
                 CVE-2022-0359 CVE-2022-0361 CVE-2022-0368 CVE-2022-0408 
                 CVE-2022-0413 CVE-2022-0417 CVE-2022-0443 CVE-2022-0554 
                 CVE-2022-0572 CVE-2022-0685 CVE-2022-0714 CVE-2022-0729 
                 CVE-2022-0943 CVE-2022-1154 CVE-2022-1616 CVE-2022-1720 
                 CVE-2022-1851 CVE-2022-1898 CVE-2022-1968 CVE-2022-2285 
                 CVE-2022-2304 CVE-2022-2598 CVE-2022-2946 CVE-2022-3099 
                 CVE-2022-3134 CVE-2022-3234 CVE-2022-3324 CVE-2022-3705
 
Multiple security vulnerabilities have been discovered in vim, an enhanced
vi editor. Buffer overflows, out-of-bounds reads and use-after-free may lead to
a denial-of-service (application crash) or other unspecified impact.

For Debian 10 buster, these problems have been fixed in version
2:8.1.0875-5+deb10u3.

We recommend that you upgrade your vim packages.

For the detailed security status of vim please refer to
its security tracker page at:
https://security-tracker.debian.org/tracker/vim

Further information about Debian LTS security advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://wiki.debian.org/LTS

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: