Vulnerability Description
Vim is an open source command line text editor. double-free in dialog_changed() in Vim < v9.1.0648. When abandoning a buffer, Vim may ask the user what to do with the modified buffer. If the user wants the changed buffer to be saved, Vim may create a new Untitled file, if the buffer did not have a name yet. However, when setting the buffer name to Unnamed, Vim will falsely free a pointer twice, leading to a double-free and possibly later to a heap-use-after-free, which can lead to a crash. The issue has been fixed as of Vim patch v9.1.0648.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Vim | Vim | < 9.1.0648 |
Related Weaknesses (CWE)
References
- https://github.com/vim/vim/commit/b29f4abcd4b3382fa746edd1d0562b7b48cPatch
- https://github.com/vim/vim/security/advisories/GHSA-46pw-v7qw-xc2fVendor Advisory
- https://security.netapp.com/advisory/ntap-20241115-0002/
FAQ
What is CVE-2024-41965?
CVE-2024-41965 is a vulnerability with a CVSS score of 4.2 (MEDIUM). Vim is an open source command line text editor. double-free in dialog_changed() in Vim < v9.1.0648. When abandoning a buffer, Vim may ask the user what to do with the modified buffer. If the user want...
How severe is CVE-2024-41965?
CVE-2024-41965 has been rated MEDIUM with a CVSS base score of 4.2/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-41965?
Check the references section above for vendor advisories and patch information. Affected products include: Vim Vim.