CVE-2022-2816: Out-of-bounds Read in vim/vim
Last updated 24 July 2024
Other sources
Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.0212.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/vimto a version that resolves this vulnerability.Fixed in 2:9.0.1378-2+deb12u2Fixed in 2:9.1.1230-2Fixed in 2:9.1.1230-2+deb13u1Fixed in 2:9.2.0858-1 - Upgrade
Upgrade
alpine/vimto a version that resolves this vulnerability.Fixed in 9.0.0224-r0 - Upgrade
Upgrade
debian/vimto a version that resolves this vulnerability.Fixed in 2:9.0.0229-1 - Upgrade
Upgrade
vim/vimto a version that resolves this vulnerability.Fixed in 9.0.0212
Event History
Frequently Asked Questions
What is the severity of CVE-2022-2816?
The severity of CVE-2022-2816 is high.
How does CVE-2022-2816 impact GitHub repository vim/vim?
CVE-2022-2816 causes an out-of-bounds read vulnerability in GitHub repository vim/vim prior to version 9.0.0212.
What software versions are affected by CVE-2022-2816?
CVE-2022-2816 affects versions 2:8.2.3995-1ubuntu2.11 and earlier, as well as version 9.0.0212 and earlier.
How can I fix the CVE-2022-2816 vulnerability?
To fix the CVE-2022-2816 vulnerability, upgrade to version 9.0.0212 or later of vim/vim.
Where can I find more information about CVE-2022-2816?
You can find more information about CVE-2022-2816 on the [CVE website](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2816) and the [GitHub commit](https://github.com/vim/vim/commit/dbdd16b62560413abcc3c8e893cc3010ccf31666) for the fix.