public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: Could we get Vim 9 packaged to fix CVEs
Date: Fri, 17 Nov 2023 15:14:29 -0700	[thread overview]
Message-ID: <bf424fdc-2f78-4182-bb92-40cd64f80414@Shaw.ca> (raw)
In-Reply-To: <122a988f-97dd-458a-9bc9-42a526e1b1e5@Shaw.ca>

On 2023-11-12 15:27, Brian Inglis via Cygwin wrote:
> On 2023-11-09 09:35, Jack S via Cygwin wrote:
>> Would it be possible to update the vim packages with Vim 9, please?

> Also now:
>      https://github.com/vim/vim/security/advisories/GHSA-q22m-h7m2-9mgm

Expanding above:

CVE-2023-46246: Integer overflow in :history Ex-Command in Vim < 9.0.2068
https://github.com/vim/vim/security/advisories/GHSA-q22m-h7m2-9mgm
fixed in Vim patch 9.0.2068
https://github.com/vim/vim/commit/9198c1f2b1ddecde22af918541e0de2a32f0f45a

New:

[vim-security] several minor security issues in Vim v9.0.2106-v9.0.2112
https://seclists.org/oss-sec/2023/q4/218

CVE-2023-48231: Use-After-Free in win_close()
https://github.com/vim/vim/security/advisories/GHSA-8g46-v9ff-c765
fixed in Vim patch 9.0.2106
https://github.com/vim/vim/commit/25aabc2b8ee1e19ced6f4da9d866cf9378fc4c5a

CVE-2023-48232: Floating point Exception in adjust_plines_for_skipcol()
https://github.com/vim/vim/security/advisories/GHSA-f6cx-x634-hqpw
fixed in Vim patch 9.0.2107
https://github.com/vim/vim/commit/cb0b99f0672d8446585d26e998343dceca17d1ce

CVE-2023-48233: overflow with count for :s command
https://github.com/vim/vim/security/advisories/GHSA-3xx4-hcq6-r2vj
fixed in Vim patch 9.0.2108
https://github.com/vim/vim/commit/ac63787734fda2e294e477af52b3bd601517fa78

CVE-2023-48234: overflow in nv_z_get_count
https://github.com/vim/vim/security/advisories/GHSA-59gw-c949-6phq
fixed in Vim patch 9.0.2109
https://github.com/vim/vim/commit/58f9befca1fa172068effad7f2ea5a9d6a7b0cca

CVE-2023-48235: overflow in ex address parsing
https://github.com/vim/vim/security/advisories/GHSA-6g74-hr6q-pr8g
fixed in Vim patch 9.0.2110
https://github.com/vim/vim/commit/060623e4a3bc72b011e7cd92bedb3bfb64e06200

CVE-2023-48236: overflow in get_number
https://github.com/vim/vim/security/advisories/GHSA-pr4c-932v-8hx5
fixed in Vim patch 9.0.2111
https://github.com/vim/vim/commit/73b2d3790cad5694fc0ed0db2926e4220c48d968

CVE-2023-48237: overflow in shift_line
https://github.com/vim/vim/security/advisories/GHSA-f2m2-v387-gv87
fixed in Vim patch 9.0.2112
https://github.com/vim/vim/commit/6bf131888a3d1de62bbfa8a7ea03c0ddccfd496e

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

  reply	other threads:[~2023-11-17 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 16:35 Could we get Vim 9 packaged? Jack S
2023-11-12 22:27 ` Brian Inglis
2023-11-17 22:14   ` Brian Inglis [this message]
2023-11-27  6:48     ` Could we get Vim 9 packaged to fix CVEs Marco Atzeri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf424fdc-2f78-4182-bb92-40cd64f80414@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).