oss-security - [vim-security] double-free in dialog

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <Zqvz6w+ReGkspALf@256bit.org>
Date: Thu, 1 Aug 2024 22:45:31 +0200
From: Christian Brabandt <cb@...bit.org>
To: oss-security@...ts.openwall.com
Subject: [vim-security] double-free in dialog_changed() in Vim < v9.1.0648

double-free in dialog_changed() in Vim < v9.1.0648
==================================================
Date: 01.08.2024
Severity: Low
CVE: <not-yet-assigned>
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

URLs: https://github.com/vim/vim/commit/b29f4abcd4b3382fa746e
      https://github.com/vim/vim/security/GHSA-46pw-v7qw-xc2f

Thanks,
Chris
-- 
Denk immer daran, daß die Menge, die bei Deiner Krönung gejubelt hat,
auch klatschen wird, wenn man Dich köpft.
		-- Terry Pratchett, "Ab die Post"

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.