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.

Vulnerability/
CVE-2017-6349

critical

9.8

CWE

190 119

27/2/2017

5/8/2024

CVE-2017-6349: Integer Overflow

First published: Mon Feb 27 2017(Updated: )

An integer overflow at a u_read_undo 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.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Vim Vim	<=8.0.0376
debian/neovim		0.4.4-1 0.7.2-7 0.9.5-7 0.9.5-10
debian/vim		2:8.2.2434-3+deb11u1 2:9.0.1378-2 2:9.1.0709-2 2:9.1.0777-1

Remedy

https://github.com/vim/vim/commit/3eb1637b1bba19519885dd6d377bd5596e91d22c

Never miss a vulnerability like this again

Reference Links

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.

collector/nvd-index
agent/type
collector/launchpad-cve
source/Launchpad
agent/author
agent/remedy
agent/severity
collector/nvd-cve
source/NVD
agent/software-canonical-lookup
agent/weakness
collector/mitre-cve
source/MITRE
agent/last-modified-date
collector/usn-cve
source/Ubuntu
agent/references
agent/description
agent/first-publish-date
agent/event
collector/security-tracker-debian
source/Debian
agent/softwarecombine
agent/trending
agent/tags
agent/source
vendor/vim
canonical/vim vim
version/vim vim/8.0.0376
package-manager/debian

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

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.