CVE-2017-6349: Integer Overflow
An integer overflow at a ureadundo 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/neovimto a version that resolves this vulnerability.Fixed in 0.4.4-1Fixed in 0.7.2-7Fixed in 0.10.4-8Fixed in 0.12.3-4Fixed in 0.12.4-1 - Upgrade
Upgrade
debian/vimto a version that resolves this vulnerability.Fixed in 2:8.2.2434-3+deb11u1Fixed in 2:8.2.2434-3+deb11u3Fixed in 2:9.0.1378-2+deb12u2Fixed in 2:9.1.1230-2Fixed in 2:9.2.0524-1Fixed in 2:9.2.0782-1 - Upgrade
Upgrade
vimto a version that resolves this vulnerability.Fixed in 8.0.0377
Event History
Frequently Asked Questions
What is the severity of CVE-2017-6349?
CVE-2017-6349 has a high severity rating due to the potential for buffer overflows resulting from integer overflow vulnerabilities.
How do I fix CVE-2017-6349?
To fix CVE-2017-6349, upgrade Vim to version 8.0.0377 or later, or apply the appropriate patches for affected versions.
What versions of Vim are affected by CVE-2017-6349?
Versions of Vim before 8.0.0377 are affected by CVE-2017-6349.
Is Neovim affected by CVE-2017-6349?
Yes, specific versions of Neovim prior to 0.4.4-1 are affected by CVE-2017-6349.
What can happen if CVE-2017-6349 is exploited?
Exploitation of CVE-2017-6349 could lead to arbitrary code execution due to buffer overflows caused by the integer overflow.