Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vim: security update to 9.1.0648 #7441

Open
MingcongBai opened this issue Aug 2, 2024 · 0 comments
Open

vim: security update to 9.1.0648 #7441

MingcongBai opened this issue Aug 2, 2024 · 0 comments
Labels
security Topic/issue involves a security issue/fixed upgrade Topic/issue involves a package upgrade

Comments

@MingcongBai
Copy link
Member

MingcongBai commented Aug 2, 2024

Affected package (and version)

vim < 9.1.0648

CVE ID(s)

CVE-2024-41957

Severity

Low

Other security advisory ID(s)

N/A

Description/References

use-after-free in tagstack_clear_entry() in Vim

Date: 01.08.2024
Severity: Low
CVE: CVE-2024-41957
CWE: Double Free (CWE-415)

When closing a window, the corresponding tagstack data will be cleared and freed. However a bit later, the quickfix list belonging to that window will also be cleared and if that quickfix list points to the same tagstack data, Vim will try to free it again, resulting in a double-free/use-after-free access exception.

Impact is low since the user must intentionally execute vim with several non-default flags, but it may cause a crash of Vim.

double-free in dialog_changed() in Vim < v9.1.0648

Date: 01.08.2024
Severity: Low
CVE:
CWE: Double Free (CWE-416)

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 Vim project would like to thank github user SuyueGuo for reporting this issue.

The issue has been fixed as of Vim patch v9.1.0648

Patch(es)/Solution(s)

Update to >= 9.1.

@MingcongBai MingcongBai added security Topic/issue involves a security issue/fixed upgrade Topic/issue involves a package upgrade labels Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security Topic/issue involves a security issue/fixed upgrade Topic/issue involves a package upgrade
Projects
None yet
Development

No branches or pull requests

1 participant