CVE-2017-6350: Integer Overflow
An integer overflow at an unserializeuep memory allocation site would occur for vim before patch 8.0.0378, 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.0378 - Compensating control
Ensure undo files are obtained from trusted sources; avoid opening corrupted/unknown undo files to prevent triggering the integer overflow in the unserialize_uep memory allocation path.
Event History
Frequently Asked Questions
What is the severity of CVE-2017-6350?
CVE-2017-6350 has a medium severity rating due to its potential to cause buffer overflows.
How do I fix CVE-2017-6350?
To fix CVE-2017-6350, update Vim to version 8.0.0378 or later.
Which versions of Vim are affected by CVE-2017-6350?
CVE-2017-6350 affects Vim versions prior to 8.0.0378.
What type of vulnerability is CVE-2017-6350?
CVE-2017-6350 is categorized as an integer overflow vulnerability.
In which scenarios can CVE-2017-6350 be exploited?
CVE-2017-6350 can be exploited when Vim processes a corrupted undo file.