From: Lester Ingber <ingber@alumni.caltech.edu>
To: cygwin@cygwin.com
Subject: vim overflow for version < 9.0 ?
Date: Tue, 12 Jul 2022 07:43:20 -0700 [thread overview]
Message-ID: <Ys2IiJh6+uCBmzY8@ingber.com> (raw)
This was just reported by US-CERT <US-CERT@messages.cisa.gov> :
We are running VIM - Vi IMproved version 8.2.4372.
Medium Vulnerabilities
vim -- vim Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0. 2022-07-01 6.8 CVE-2022-2264
MISC
CONFIRM
vim -- vim Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0. 2022-07-02 6.8 CVE-2022-2284
CONFIRM
MISC
vim -- vim Integer Overflow or Wraparound in GitHub repository vim/vim prior to 9.0. 2022-07-02 6.8 CVE-2022-2285
MISC
CONFIRM
vim -- vim Out-of-bounds Read in GitHub repository vim/vim prior to 9.0. 2022-07-02 6.8 CVE-2022-2286
CONFIRM
MISC
vim -- vim Out-of-bounds Read in GitHub repository vim/vim prior to 9.0. 2022-07-02 5.8 CVE-2022-2287
MISC
Lester
reply other threads:[~2022-07-12 14:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Ys2IiJh6+uCBmzY8@ingber.com \
--to=ingber@alumni.caltech.edu \
--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).