USN-6993-1: Vim vulnerabilities

Published Sep 5, 2024
·
Updated

It was discovered that Vim incorrectly handled memory when closing a window, leading to a double-free vulnerability. If a user was tricked into opening a specially crafted file, an attacker could crash the application, leading to a denial of service, or possibly achieve code execution with user privileges. (CVE-2024-41957) It was discovered that Vim incorrectly handled memory when adding a new file to an argument list, leading to a use-after-free. If a user was tricked into opening a specially crafted file, an attacker could crash the application, leading to a denial of service. (CVE-2024-43374)

Affected Software

12 affected componentsFixes available
All of the following
ubuntu/vim<2:9.1.0016-1ubuntu7.2
2:9.1.0016-1ubuntu7.2
Ubuntu Ubuntu=24.04
All of the following
ubuntu/vim<2:8.2.3995-1ubuntu2.18
2:8.2.3995-1ubuntu2.18
Ubuntu Ubuntu=22.04
All of the following
ubuntu/vim<2:8.1.2269-1ubuntu5.24
2:8.1.2269-1ubuntu5.24
Ubuntu Ubuntu=20.04
All of the following
ubuntu/vim<2:8.0.1453-1ubuntu1.13+esm9
2:8.0.1453-1ubuntu1.13+esm9
Ubuntu Ubuntu=18.04
All of the following
ubuntu/vim<2:7.4.1689-3ubuntu1.5+esm24
2:7.4.1689-3ubuntu1.5+esm24
Ubuntu Ubuntu=16.04
All of the following
ubuntu/vim<2:7.4.052-1ubuntu3.1+esm18
2:7.4.052-1ubuntu3.1+esm18
Ubuntu Ubuntu=14.04

Event History

Sep 5, 2024
Advisory Published
via Ubuntu·12:00 AM

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of USN-6993-1?

The severity of USN-6993-1 is high due to its potential to lead to denial of service or arbitrary code execution.

2

How do I fix USN-6993-1?

To fix USN-6993-1, update Vim to the recommended version for your Ubuntu release as detailed in the advisory.

3

Which versions of Vim are affected by USN-6993-1?

USN-6993-1 affects multiple versions of Vim across Ubuntu 14.04 to 24.04.

4

What is a double-free vulnerability as mentioned in USN-6993-1?

A double-free vulnerability occurs when an application erroneously frees the same memory location twice, potentially leading to crashes or execution of malicious code.

5

What should I do if I cannot update Vim to mitigate USN-6993-1?

If you cannot update Vim, consider avoiding the use of untrusted files with Vim until the issue is resolved.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203